Maybe I missed it, but I can't seem to find the answers to a few questions about deploying R3. I've got SCCM SP2 R2 running on Win08R2x64 with SQL08sp1 STD. Does KB977384 ever require a reboot? What client OSs require KB997834 for a R3 update? x86 x64? Does R3 configure the clients for WoL?
October 18th, 2010 9:47pm
Not sure about most of your questions but I can say that R3 will not configure your clients BIOS for WOL if that's what you are asking. If you happen to have Dell computers there's a util available from Dell that will handle that. John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
October 18th, 2010 10:10pm
I'm not worried about BIOS configuration, we'll use the DCCU to get that done for imaging. When we tested the R3 beta in the lab it did not configure the network adaptors for WoL, but it looks like the RTM does, I just want to confirm it. As to the KB997384 questions, I would prefer to keep all my cleint at the same client version, but I have to be sure I don't reboot any servers. When we switched to SUP for updates from WSUS, the requirement for the latest WUA caused a few problems. So I'm trying to avoid "problems" .
October 18th, 2010 10:17pm
Hi, 1# You do not have to restart after you apply the KB977384. 2# All you need about R3 supported config is here http://technet.microsoft.com/en-us/library/ff977062.aspx 3# I agree with John
October 18th, 2010 10:23pm
Hi, 1# You do not have to restart after you apply the KB977384. 2# All you need about R3 supported config is here http://technet.microsoft.com/en-us/library/ff977062.aspx 3# I agree with John Thanks for the info about 997834 not causing reboots, that just made my deployment much easier. But my question about OSs was not about SCCM R3 supported OSs, but what OSs need KB997834. And I'm still not sure I have a answer about R3 configuring the Windows Network Adapter driver for WoL
October 18th, 2010 10:53pm
But my question about OSs was not about SCCM R3 supported OSs, but what OSs need KB997834. And I'm still not sure I have a answer about R3 configuring the Windows Network Adapter driver for WoL The info is in the link, we install the hotfix on clients to use power management and all OS that supports this feature are under "Operating Systems Supported by Power Management" And as already John said, R3 will not configure your clients BIOS for WOL, it is not exists in R3 features http://blogs.technet.com/b/systemcenter/archive/2010/10/14/system-center-configuration-manager-2007-r3-unleashed.aspx For more info about WOL http://technet.microsoft.com/en-us/library/bb693668.aspx
October 18th, 2010 11:34pm
Well, after testing, it seems KB977834 does need a restart, altho it does not force a restart. I installed the KB on my site server with verbose logging with this command line. MSIEXEC.exe /i SCCM2007-SP2-KB977384-ENU.msi /l*v %temp%\R3_Hotfix_Installation.log And noted in the log file this entry Property(C): MsiSystemRebootPending = 1 Also the automatically created softare distribution package for KB977384 was set for after running to "Program Restarts Computer" By the way the above command line also resolved a 1603 error I was getting on a XP SP3 test system. So does KB977384 actually need a restart to function, but it is supressed?
October 19th, 2010 6:10pm
Property(C): MsiSystemRebootPending = 1 That is just a property listing and has nothing to do with an actual reboot. All property listings within msi logfiles can be safely ignored. The package is set to "program restarts computer" because it might be possible that the SMS Agent Host service is restarted (which does look like a reboot from a ConfigMgr point of view). What does your logfile say at the end (error code)? Is it 0 or 3010 / 1641 (which indicate a reboot)? Plus: there is no one fits all answer: a reboot might be needed in one environment, but not the other, depending on the exact configuration.
October 19th, 2010 6:27pm
Hi Torsten, thanks for the tip about Property listings. I'll remember that. Status was 0, which looked good, I'm just being paranoid I guess. :)
October 19th, 2010 6:39pm