I've used a script from a blog somewhere, don't ask me which one now.

Basically you need the steps in the TS, a package with the content, agent
and hotfix, that script in it, run the script in the TS, it populates the
variable and the client automatically patches itself as part of the client
install.

 

Works good.

 

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Marcum, John
Sent: Montag, 30. September 2013 18:01
To: '[email protected]'
Subject: RE: [mssms] CU3, agent installation issue

 

Sorry if this has been asked and answered, this has been a long thread and I
had a long weekend.. Is there a way to specify the PATCH property during the
client install in OSD so that the client is updated upon installing?

 

 

 

 

 

  _____  

John Marcum
Sr. Desktop Architect

Bradley Arant Boult Cummings LLP

  _____  

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Friday, September 27, 2013 3:05 PM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Ahh, got it. I will test that out in my 2nd build I am doing this weekend. 

 

Daniel Ratliff

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Friday, September 27, 2013 3:57 PM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Let me try again. J

The client on the site server, only on the site server and only when
installed after CU3 is applied to them and only a fresh install of the RTM
client, not an upgrade to CU3.

 

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Freitag, 27. September 2013 17:12
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Doh, I just realized you are talking about the client, not the site install.
I can test that pretty easily, I setup a deployment last night to update all
my clients to CU3 so I should see it as soon as I get home if it failed.
I'll let you know. 

 

Daniel Ratliff

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Friday, September 27, 2013 11:03 AM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Wait a second, for this to show for me:

Have SP1, CU3 installed, single primary

Install the agent on the site server. This fails for me.

If the agent is already installed prior to CU3, uninstall and install the
agent again. Also fails for me.

 

Did you try that?

 

 

 

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Freitag, 27. September 2013 14:54
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

I upgraded my SP1 CU2 site to CU3 last night, no issues. It did throw me a
bit that the site version still shows 5.0.7084.1000 though, I didn't realize
that doesn't change on the CUs, only clients and consoles. 

 

I will be doing the SP1 no CU to CU3 install this weekend. I should know by
Monday!

 

Daniel Ratliff

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Friday, September 27, 2013 8:01 AM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

And did you?

 

-R

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Mittwoch, 25. September 2013 19:45
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Will do.

 

Daniel Ratliff 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Wednesday, September 25, 2013 1:40 PM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Don't think so. The client install fails only on the site server, not on
other systems.

It is very specific. Might need to give them a call.

 

If you can please try it yourself.

After CU3, uninstall  the client from the site server and install again.

 

I only used smssitecode as parameter.

 

-R

 

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Mittwoch, 25. September 2013 17:31
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Hmm, I wonder if CU2 or something is a requirement? Perhaps there is
different media for the full install instead of the upgrade?

 

I haven't installed at home yet, might do that this week and see.

 

Daniel Ratliff

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Wednesday, September 25, 2013 11:19 AM
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

Don't know. I didn't get a wmi error at all and since it is also the server,
a wmi issue might show up even more.

 

I've now installed with CU2 (all ok again), upgraded to CU3, also the client
on the server, still ok.

It just breaks when starting with CU3.

 

I bet when uninstalling the agent and installing again it breaks again. Have
to try that.

Just tried, uninstall, install (rtm), fails.

 

-R

 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: Mittwoch, 25. September 2013 13:46
To: [email protected]
Subject: RE: [mssms] CU3, agent installation issue

 

May be related, corrupt WMI repository.

 

http://support.microsoft.com/kb/2465990 

 

Daniel Ratliff 

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Roland Janus
Sent: Wednesday, September 25, 2013 4:58 AM
To: [email protected]
Subject: [mssms] CU3, agent installation issue

 

I can repeat that issue. Procedure:

 

Install a single CM12 SP1 primary on Server 2012, SQL 2012 SP1CU6

Install CU2

Install the agent on the server. All is ok.

 

Do the exact same with CU3, once installing the agent I get this:

 

MSI: Setup was unable to register the CCM_Service_HostingConfiguration
endpoint

The error code is 80041002

 

It never recovers from that.

 

Anyone seen that or ideas?

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

  _____  


Confidentiality Notice: This e-mail is from a law firm and may be protected
by the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and
then delete it from your computer.

 

  _____  


Confidentiality Notice: This e-mail is from a law firm and may be protected
by the attorney-client or work product privileges. If you have received this
message in error, please notify the sender by replying to this e-mail and
then delete it from your computer.

 



Reply via email to