Secondary site advanced clients assigned to primary site code.
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
In my environment we upgraded from SMS 2.0 to SMS 2003 SP1. We have one
primary site called NY1 and three secondary sites called LN1, TK1 and SG1.
In SMS 2.0 our legacy clients were assigned to their respective site codes.
When we upgraded to the Advanced Client, all clients are assigned to the
primary site code. Is that normal? If not, how do I change it.
.
Relevant Pages
- Migration Questions
... Collections are populated using site codes. ... Upgrade Central Site to SMS 2003 ... Clients in the secondary sites are still SMS 2.0 clients ...
(microsoft.public.sms.admin) - Re: SMS 2003 SP1 - Cross Forest Clients and Advanced Security
... If you want to use the Advanced client network access account, ... > situation is regarding hotfix Q325804. ... Since all of the remote forest clients ...
(microsoft.public.sms.setup) - Re: Upgrade SMS 2.0 to SMS 2003 to new hardware without losing old data
... Clients should be used. ... I need to keep all my data from the sms 2.0 central server (queries, ... Make boundaries of old secondary servers to boundaries of new secondary ... Distribute SP2 advanced client to all clients via software ...
(microsoft.public.sms.setup) - Re: Secondary sites, Management Points and IIS
... but you're Advanced Clients will fall back to their ... > "Installing a proxy management point at the secondary site can significantly ... > Configuration and Operation of Advanced Client Roaming: ... >> I have one Primary site and a great number of Secondary sites at ...
(microsoft.public.sms.setup) - Re: SMS management of systems in a workgroup
... for Advanced Clients you would want the Advanced Client Network Access ... not the software installation account. ... to access the distribution points of the site server. ... We have installed the advanced client on them. ...
(microsoft.public.sms.admin) |
|
