SP3 - Packages Not Allocating CC3

[Hightower]

Morning folks,

 

I've just done the SP3 updates here as per RM instructions. I've also slipstreamed SP3 into the build image on the server.

 

Everything seems fine apart from the RM packages (such as RM LST etc) don't allocate straight away. Once the machine has built and the logon screen is shown, I have to restart each machine once more to pick up the RM packages that were left off.

 

Anyone got any idea what this could be and how to resolve it?

 

Thanks,

[CyberDrac]

There's a fix which is needed in some cases, where some packages are dependent on "Windows Installer 3.1" being installed and the CC3 SP3 install is causing an issue, I believe the fix may be to add the dependency into the .ini file for the CC3 SP3 for Windows Installer 3.1. There is a TEC article for this.

 

edit: TEC1677288, and TEC1675386 may be of interest.

Edited August 20, 2010 by CyberDrac

[Hightower]

I saw that but figured that wasn't technically my problem. SP3 is installed as part of the build (slipstreamed) so technically the SP3 RM package shouldn't need to allocated because it's already on, therefore I shouldn't need to tweak dependencies - if that makes sense?!

[Sylv3r]

You could add the line

 

reboots=1

 

To one of the package .ini files that installs first time which will reboot the workstations which will in affect continue to install the missing RM LST packages etc.

[soapyfish]

@ Sylv3r would you need to add this line to the ini file for the last package it installs before needing the reboot or would anyone do ?

[Sylv3r]

Wouldn't like to say to fix the above problem, but any package with this line will be the one it reboots straight after.

[sandeep2504]

@hightower

 

did you manage to fix this in the end?

 

im in a similar situation

 

smartclienting a windows xp sp3 pc

 

the sp3 machines are in a different container to the sp2 images

 

the pc smartclients fine then a couple reboots later it sits on the logon screen tried to restart and nothing

 

the only way around is run installrm or restart the autoexnt server and i have to do this every single time it reboots

[Hightower]

No - haven't had chance to take a look even with so much else going on here. Let me know if you get anywhere with it please.

 

Thanks,

[gl3nnym]

We had a problem where after installing SP3 no network packages were installing on a specific brand of laptop. Everything else was fine but this one brand where we had to manually "installrm".

 

Turns out it was an incompatibility with SP3 and the wireless driver.