|
skissinger -> RE: Upgrade SMS2k3 Secondary site to SCCM (10/2/2008 2:49:19 PM)
|
Those were the easy ones. Well, I didn't have an legacy clients. Do you have any legacy clients? Maybe you'd have more to worry about then. I only had about 9; and I'm a control freak, so I had replicated the source files locally to the box (just as a package, so it went to smspkgX$\somefolder); and ran the upgrade via an RDP connection. Those happened to be proxy MPs, so I just had to watch the mpsetup.log file, and I did an update DPs of my super-small test package post-upgrade to test the dp stuff. I suppose I should have asked... they're going to belong to the same primary site, right? You're not moving them to another one (side-by-side)? If so, then there are more steps involved, but I've done that before too. My best time was 2.5hrs of time, and overnight to let the packages sync up after doing preloadpkgonsite.
|
|
|
|