SCCM SP2 Upgrade.
Hi All, We are planning to upgrade the sccm (currently we have R2 with SP1), we are upgrading to SP2. We did upgrade in our lab and it went good, upgrade was successful. when we used it in pre-production environment, which is almost similar to production environment. Installation was successful after a long wait. But Once the installation was completed, we started checking the functionality of SCCM and found two major issues. Package is not getting distributed, not even to Distribution point which is sccm server itself and to BDP.None of the advertisement is visible when login to the console through terminal server(we are using and the console is installed in it). For Issue1: When we tried to find the root cause we found in distmgr.log that SCCM is contacting all the BDPs and trying to reset them. It took 2 days to completely check all the BDPs and reset them (in production it will take much more compared to this as we have almost 1000 BDPs). Checked in Microsoft site and found this is a known behavior and before we upgrade we will have to take care of few things which is mentioned in the below KB article. http://support.microsoft.com/kb/969163 The question is: Is the reset of distribution points a necessary step? i.e. would preventing this step add any risk. For what purpose is SCCM accessing packages on the DPs? Tried to find the answer in web but unfortunately dint get any satisfactory answer. Any help on this would be highly appreciated. For Issue2: We got to know that we need to upgrade the console in terminal sever, and we will do that. Thanks, Abhishek Yadav
April 4th, 2012 9:20am

I have done several SP2 upgrades and I have never seen the issue you run into. The questions is, how close is the Lab environment to your production environment? Lab environments are often not maintained and does not reflect production at all. I would start by running the prereq checker and fix any errors/warnngs that is displays. Furthermore also make sure you have a recent backup of the CM07 environment.Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2012 12:07pm

Hi Kent, Thanks for your time and reply, to answer your questions, how close is the Lab environment to your production environment?: our pre-production is environment is always kept similar to prduction environment except the number of machines and number of user which will be lower pre-production. we have ran the pre-requisite checker and it took too long to complete, completed without warning or errors. looks like it is trying to contact all the machines (site systems with BDP role)and changing some registry settings OS version. Pre-req log: <03-27-2012 11:58:00> Connecting to registry on site system [\\CA800003], site code [RS2] <03-27-2012 11:59:47> Connected to registry on site system [\\CA800003], site code [RS2] <03-27-2012 11:59:47> ---> System OS version string "5.1" converted to 5.10 <03-27-2012 11:59:50> Connecting to registry on site system [\\CA800004], site code [RS2] <03-27-2012 12:00:08> Connected to registry on site system [\\CA800004], site code [RS2] <03-27-2012 12:00:09> ---> System OS version string "5.1" converted to 5.10 <03-27-2012 12:00:10> Connecting to registry on site system [\\CA800006], site code [RS2] <03-27-2012 12:00:56> Could not connect to registry on site system [\\CA800006], site code [RS2] <03-27-2012 12:00:56> Connecting to registry on site system [\\CA800022], site code [RS2] <03-27-2012 12:01:02> Could not connect to registry on site system [\\CA800022], site code [RS2] <03-27-2012 12:01:02> Connecting to registry on site system [\\CA800044], site code [RS2] <03-27-2012 12:01:56> Could not connect to registry on site system [\\CA800044], site code [RS2] we have 1000s of machines with BDP role. Below is the log from distmgr.log ~Setting HTTPUrl to blank for package RS2002FC on DP \\NO80000501\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:04.410 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS2002FF on DP \\NO80000501\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:04.457 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200312 on DP \\NO80000501\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:04.551 2012 W. Europe Daylight Time><thread=4756 (0x1294)> Successfully modified DP ["Display=\\NO80000501\"]MSWNET:["SMS_SITE=RS2"]\\NO80000501\ Drizzle Role to 0 $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:05.098 2012 W. Europe Daylight Time><thread=4756 (0x1294)> for ["Display=\\NO80000601\"]MSWNET:["SMS_SITE=RS2"]\\NO80000601\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:05.098 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS20028D on DP \\NO80000601\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:08.926 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200290 on DP \\NO80000601\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:08.957 2012 W. Europe Daylight Time><thread=4756 (0x1294)> Successfully modified DP ["Display=\\NO80000601\"]MSWNET:["SMS_SITE=RS2"]\\NO80000601\ Drizzle Role to 0 $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:10.207 2012 W. Europe Daylight Time><thread=4756 (0x1294)> for ["Display=\\NO80000801\"]MSWNET:["SMS_SITE=RS2"]\\NO80000801\, machine account is to be used~ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:10.207 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS2000C7 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:11.379 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS20013A on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:11.988 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200150 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.098 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS20017E on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.441 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200182 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.473 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200185 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.488 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200188 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.520 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200191 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:12.582 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS20026A on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:14.395 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200286 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:14.754 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200312 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:15.754 2012 W. Europe Daylight Time><thread=4756 (0x1294)> ~Setting HTTPUrl to blank for package RS200317 on DP \\NO80000801\SMSPKGD$ $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:15.785 2012 W. Europe Daylight Time><thread=4756 (0x1294)> Successfully modified DP ["Display=\\NO80000801\"]MSWNET:["SMS_SITE=RS2"]\\NO80000801\ Drizzle Role to 0 $$<SMS_DISTRIBUTION_MANAGER><Tue Apr 03 06:22:16.520 2012 W. Europe Daylight Time><thread=4756 (0x1294)> I hope these logs will help you in understanding what is happening in our environment and help me with this. Thanks and regards, Abhishek Yadav
April 5th, 2012 2:48am

Can't offer insight to question #1, but I know exactly what the issue is with question #2... You need to upgrade the SCCM admin console on your Terminal Server(s) to SP2. An SP1 SCCM admin console will not be able to display any advertisements when your SCCM back-end is SP2. I don't remember if I've ever seen any documentation that describes this quirk, but that's what you are seeing. Nick.
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2012 11:28pm

Thanks Nick, Thanks for your reply, if you or anyone else come across with an answer that will be great help as our upgrade is on hold for the answer as we dont want to be in trouble after making registry changes and removing the resetisapi.trn before we upgrade. Thanks, Abhishek Yadav
April 6th, 2012 3:01am

The question is: Is the reset of distribution points a necessary step? i.e. would preventing this step add any risk. For what purpose is SCCM accessing packages on the DPs? Tried to find the answer in web but unfortunately dint get any satisfactory answer. Any help on this would be highly appreciated. Is the reset of distribution points a necessary step? i.e. would preventing this step add any risk. Not necessary, it is why why that KB said it can be disabled to optimise the upgrade experience. For what purpose is SCCM accessing packages on the DPs? I think the KB summarises that. If your issue is the same as that in the KB then this is just DistMgr doing a check of the packages and verifying their available but taking ages to do it hence the patch that is mentioned
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2012 1:36pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics