Welcome to the Blogcast Repository Sign in | Join | Help
Search BlogCastRepository.com for:
in Search

239 BlogCasts in The BlogCast Repository!

Browse Albums

How to Upgrade from SMS 2003 SP2 to SP3

You must be a registered user in order to view any videos on The Blogcast Repository. Please either sign in or register to continue.

Sign in

(I forgot my password)
Sign in »
Not a member yet? Click here to Join
Downloads: 4,943 File Size: 20,849,603
Posted By: Brian S. Tucker Views: 7,734
Date Added: 04-30-2007

If you have yet to read about the new features in SP3, you need to get up to speed whether you are upgrading or installing SP3 for the first time. The install notes for SP3 are a bit under the radar by my opinion, so here is my install guide to SP3. Whether you are doing an upgrade or a clean install, the process is almost the same. I don't plan on doing another Blogcast on a clean install as the SP2 blogcast and the SP3 blogcast are very similar. Some of the key things you should know about SP3 are as follows:

1. Install SP3 in a test environment. This is almost required to make sure your environment is proper and meets the requirements of SP3.

2. Validate your production environment is clean or at least functioning properly. The Blogcast shows how to validate your MP is installed and running as designed. Also make sure a few clients are running properly. In the Blogcast, we show how to validate this in short detail.

3. Installing SP3 is very straight forward. If you already have SP2, the upgrade is clean; however, you should watch to see how the log files upgrade and which ones to look out for.

4. Once the install is complete, validate the SMSSetup.log file for any possible errors. This holds true for clean installs of upgrades. Check your MPSetup.log for successful installation as well as your MPControl.log. As with any validation, you have to make sure that your environment is clean before the upgrade and after. The Blogcast shows my process to make sure everything is running smooth.

5. How to install the new SP3 Advanced Client on the Primary server and validate proper installation.

6. Once SP3 is installed and running, how to do a Client Push to Windows 2003 Server, XP SP2 and Vista are all demonstrated in the Blogcast. If Vista is your intended OS to install SMS to, you need to make sure you have the firewall disabled or the proper ports opened to install the SMS client. Please make sure you test this in your lab. I can bet money that this will be a huge issue for many environments. Once again, test, test, test.....

7. Which log(s) show proper installation on the client? Check the following.... ClientLocation.log, LocationServices.log and finally the Execmgr.log. If the Execmgr.log file does not show Software Distribution Enabled... the client is not fully installed. Once again, this is shown in the Blogcast.

Although SP3 just came out today, there will be a lot to follow, but the video is more than enough to get you through the hump. Once again, make sure you test the install so you know what to expect and also make sure that you watch the Blogcast to know exactly what not to do.

Please post any questions you may have in the SMS 2003 forum! Continue to check out my blog for more info on SP3 as it's released!

Comments

 

Nathan said:

I notice that you installed the SMS client via the msi directly. I read that its a good idea to allways install the client using the ccmsetup wrapper due to self-heal issues when upgrade time comes around again.
05-01-2007 8:32 AM
 

Nathan said:

Oh, and great blogcast! i always watch them all. :)
05-01-2007 8:34 AM
 

Brian S. Tucker said:

I have heard and read several things about that. I do tend to use client push for regular systems. My SMS servers are always closely managed by me, so I have never run into a problem. Happy you like the video!
05-01-2007 10:25 AM
 

JDA said:

Very informative. Good info about what to view in the logs for success! Thanks for putting that together.
05-01-2007 12:02 PM
 

smartinezpr said:

This is totally awesome i was looking to write something about SP1 to SP3, but you guys are awesome. Keep on the Good Work. Santos
05-01-2007 3:23 PM
 

SnowManson said:

I'm curious why you didn't do a -testdbupgrade prior to the actual upgrade. Is it because this is only a lab environment. Would you still suggest doing this in production?
05-02-2007 12:11 AM
 

DMC said:

I am currently running SM 2003 SP1, without any FPs, or ITMU. The SP2 upgrade steps included additional hotfixes that had to be installed on both the clients and servers before the SP could installed. Does SP3 still have that issue? Are the MSI 3.1 & WUA 5.8 updates included in the Advanced client / ITMU install, or do they need to be pushed out first?
05-02-2007 1:31 PM
 

Brian S. Tucker said:

Hmm.. Been a while since I worked with Sp1. I don't know if you can upgrade clean to SP3 from SP1. You should check into that. I'm anal and would do each if it was me... but that's another conversation. LOL. I have not seen any of the issues you are talking about with Sp3. I think MSFT learned their lesson the last time and everything is much cleaner now.
05-02-2007 5:54 PM
 

Brian S. Tucker said:

SnowManson - Yea, I don't tend to do every step outlined by MSFT. I don't think you have to. What you saw in my lab video should be just as good in a production environment. I got an email yesterday that after someone watched the blogcast, they upgraded 14 sites and 2,000 clients in one day. So, I leave it to you to decide. However, each environment is different and you should always test your plan in a lab. That's my CYA statement.. :)
05-02-2007 5:56 PM
 

Pedro said:

Very good blogcast. Really helpfull watching it before testing the new SP. A couple of questions. Would you use the Push install from the central site in the hierarchy to upgrade 25000 clients from SP2 to SP3? We have 15 primary site servers and 85 secondaries, and we plan to create an SMS package with the client software msi and distribute it to the clients in order to migrate the clients to SP3. In the video when you right click on the Vista client after installing the new SP3 client the option "Start Remote Tools" does not appear in the menu (only "Start remote desktop client" is available). Do you now if it is possible to remotely control a Vista client when a user is logged on, asking for permission to the user, as it was the case with XP?
05-08-2007 5:57 AM
 

Jonathan said:

Very good to see it in action. I intend to upgrade all servers first as you suggest, starting with the central server, then down the hierarchy. I am interested to know what functionality is lost if you choose not to upgrade the clients, i.e. is it essential to upgrade the client. I want to target Vista machines only with SP3 client, and leave all existing on SP1. Can you see any problems with doing that? I ask this as the upgrade to the client is not automatic, nor desired at this site. Thanks.
05-08-2007 3:14 PM
 

Brian S. Tucker said:

Pedro - I "believe" any site that has client push enabled, will install to the resource. I don't think the client would install from the primary to a resource in a lower secondary unless CP is not enabled. You can test this on a client and look at the ccmsetup.log file to see where it's downloading from. Remote Control is NOT available in Vista. They should have done that in XP as MSFT suggests that you use remote assistance.
05-08-2007 5:59 PM
 

Brian S. Tucker said:

Jonathan - Give me 1 good reason not to upgrade your SP1 clients? You probably have a reason, but I would upgrade all of them ASAP. Still - why stick with SP1? You have bugs that are fixed... and SP1 clients wont work with the SP2 schema and probably a dozen other things I can't think of off the top of my head.
05-08-2007 6:02 PM
 

Brian S. Tucker said:

I had the opportunity to upgrade 2 primary sites and 7 secondary sites today. It went well. I do have one MP giving me a problem, but other than that.. it looks clean. I did get a prompt on my central primary that a reboot was required after the client was installed, but did not on any other site server nor any of the 400 clients I have so far. Just a FYI for those of you looking to upgrade.
05-08-2007 6:05 PM
 

Pedro said:

Thanks very much for your help. One comment. My concern about using Push Install from the central site to upgrade the clients in a huge hierarchy was related to bandwidth comsumption. I think that using an SMS package to update the clients gives you much more control: the client downloads the package from the nearest DP in the hieararchy. To have a similar control using CP the process should be launched from every site server in the hierarchy to update only those clients assigned to that particular site. I think that updating the clients in a big hierarchy with low bandwidth WAN links using CP from the central site you could be running the risk of saturating the WAN links.
05-09-2007 12:09 PM
 

Brian S. Tucker said:

You can use the agent as a package. I have done it a few times. Once again, if you have CP enabled on each site server, it will install local too.
05-09-2007 7:29 PM
 

Bruce said:

I read that SP3 client only works on XPSP2. Is this correct? Can I still upgrade the server and XPSP2 clients while leaving all by XPSP1 machines with SP2 client?
05-30-2007 2:30 PM
 

Fernando Cezar said:

It was a very intersting video. You guys are doing a pretty good work on those videos. My experience on those upgrade are growing so much when I do any research in this forum. Tks.
06-01-2007 3:46 PM
 

Ivan Versl said:

Great video! I installed yesterday the SP3 and with this video I got some additional background information on the client stuff. Thanks!
06-13-2007 9:30 AM
 

Roney said:

Can we attach a SMS 2003 SP3 Primary site to a SMS 2003 SP2 site ? Please suggest..
06-19-2007 4:11 AM
 

Snow_Dog said:

Great video Brian, informative as always. Thanks for doing that. Do you think there will be any problems upgrading to SP3 if the site database resides on a separate server which also hosts other databases? I don't think the upgrade would affect the other databases, but I would like to hear from someone who upgraded in this type of environment, or anyone who would know. Thanks!
06-20-2007 10:29 AM
 

Brian S. Tucker said:

Roney - I would suggest all sites be on the same SP. Dog - I have not seen or heard of SP3 causeing negative impact to the DB if it's on the same or another server.
06-20-2007 10:42 AM
 

D. Lightner said:

I have tested SMS sp3 in a lab enviroment with primaries and secondaries, Looks nice in a Lab. Now the real world. I have 3 Primary sites 75 Secondary. The 3 Primaries had SMS SP2 R2 and SQL 2000. They were first upgraded to SQL 2005 SP1. After Sql 2005 was installed, Status messages stopped working. Found an article where I had to Modify a Stored procedure and this fixed Status messages. Then we waited a week to make sure every thing worked. Next we upgraded all 3 Primaries to SMS SP3, Status Messages Broke again, Had to Re-Modify Stored Procedure again in SQL 2005 SP1. Then we waited a week. It seemed to be working, Then we upgraded 5 Secondary sites to SMS SP3, 2 out of 5 failed and have been down ever since. The Proxy Management points are failing with error 500. They were working with SMS SP2 for 2 years (sms2003 & SMS 2003SP1). I have been working on trying to fix the MP's BEFORE, I try to install SP3 on 70 more servers.
06-26-2007 8:00 AM
 

bigJohn said:

Hi Brian thanks for the Vid, very informative. Can I upgrade direct from SP1 to SP3 and what are the consequenses for Advanced clients that do not reach the minimum spec (We have some 2000 machines that have to stay on sp3 for applications to work)
08-06-2007 12:22 PM
 

Maaoud said:

Brian, I wan to install the sms 2003 sp3 client on my site. 1 primary and 2 secondaries. My question is : When i install the sms client in sp3, is there an upgarde or the client.msi file of sms 2003 sp3 can be install without any installed version; (Please excuse me for my english)
09-12-2007 3:32 AM
 

Sharon said:

I have upgrade from sms 2003 sp2 with sql 2k5 to sms2003 sp3. the upgrade seems to complete Successfully, but when i tried to open reports i got an error message "You are not authorized to view this page". I checked the iis permissions and they looks ok.
10-10-2007 9:54 AM
 

Brian S. Tucker said:

Verify your AD account is in the local SMS Reporting Users group. If that's not it, uninstall the reporting point by unchecking the role, click apply, recheck the box, click apply and then OK. It should remove it and reinstall.
10-11-2007 12:17 PM
 

SANJAI said:

I need to install sms 2003 with sql 2005 database. can u let me knoew the procedures. i mean any known issues. i have sms2k3 with sp3, in u r previous blogs i have seen that u have suggested to upgrade to sql 2005 after getting the sms 2003 server running with sql 2000. thanks in advance, SANJAI.
03-31-2008 1:25 AM
 

Glen0994 said:

This blogcast appears to have been removed - anybody know where I might get a copy? - many thanks
06-11-2008 2:26 AM
 

Brian S. Tucker said:

The video plays fine. Are you getting an error? In orcer to watch any of the videos, you have to have port 88 open for the video to stream. Chances are that your company has it blocked.
06-12-2008 7:51 AM
 

Glen0994 said:

Brian - many thanks for the reply, you're exactly right - port 88 has been blocked from my place of work
06-13-2008 2:48 AM
 

lbroxterman said:

Brian - Great video. I am running SMS SP2 but after watching your video I have noticed that my clients show the client version of 2.50.3174.1152 is this not an SP2 client version?
06-19-2008 10:52 AM
 

Brian S. Tucker said:

Client Versions 2.50.3174.1152 – SMS SP1 with ITMU Hotfixes Check out this link...http://netsaber.wordpress.com/2006/06/29/sms-2003-advanced-client-versions/
06-19-2008 11:18 AM

 
 
© 2005- 2008 Systems Management Resources, LLC: Terms of Use