Re: Upgrade SMS 2.0 to SMS 2003 to new hardware without losing old data

Hi Kim,

thanks so much for your help!!!

But every day there are appearing more and more questions, so if you
don´t mind here is another one:

I intend to bring my secondary 2.0 SP5 server to new HW with new server
name and new SMS version (SMS2003 SP2). That server is responsible for
about 30 clients only. Whats the best way to do it? Is it possible?
Can I simply stop all client installation methods and then run
preinst.exe /delsite sitecode parentcode on my secondary server, then
install sms 2003 SP2 on the new server with new name and make it a
secondary of the primary with same sitecode? (Of course I would upgrade
the primary one first!) Then distribute the new advanced client to the
clients of that secondary site? Is it necessary to add the boundaries
of the old secondary site to the primary site before deinstalling it
and then add it to the new secondary server when it is installed and
remove it from primary server again? Does this prevent the clients from
deleting the info of previous installed packages? Is those information
preserved when updating 2.0 clients to 2003 clients?

Another question:
We have subnets configured for AD sites. But there are some subnets
defined as follows:
xxx.xxx.xxx.12/23 which means subnet xxx.xxx.xxx.11 and xxx.xxx.xxx.12
as far as I know. Can SMS handle that when having configured site
boundaries as ad sites?

Thanks again for your help. Hopefully it was the last time ;-)


Best regards,
Baludinger

.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Secondary Sites
    ... you cannot assign clients to them. ... Check out the SMS Technical FAQ: ... Can the advanced client talk to the existing primary site server if ... You mention that you have a child domain within your LAN. ...
    (microsoft.public.sms.setup)
  • Re: Inplace Upgrade os SMS2.0 to 2003
    ... > Currently our SMS 2.0 Installation consists of a Central Site Server and one ... On the Central Site server there are roughly 700+ clients, ... > another server that is being used as a SMS Distribution Point. ... Site boundaries should be retained after the upgrade. ...
    (microsoft.public.sms.setup)
  • Re: Networked Office
    ... || Microsoft MVP - Sharepoint Portal Server ... those 10(or 100 workstation) will get updated instantly without ... workstation from that Admin Installation. ... my next suggestion) is that when you want to update the clients ...
    (microsoft.public.office.setup)
  • Re: Networked Office
    ... || Microsoft MVP - Sharepoint Portal Server ... those 10(or 100 workstation) will get updated instantly without ... workstation from that Admin Installation. ... my next suggestion) is that when you want to update the clients ...
    (microsoft.public.windows.server.general)
Loading