SITEVER.INI

[BobS53]

Is their any way to control which site Code is configured to be the "Site supplying CLICORE=XXX"

Below is an example of a SITEVER.INI (generated in C:\TEMP)

[Client Versions]
C:\WIN\MS\SMS\CORE\BIN=2.00.1493.3188

[\\<servername>\SMSLOGON]
Site supplying CLICORE=X28

[Site Versions]
X28=2.00.1493.3188
X01=2.00.1493.3188
X02=2.00.1493.3188
X03=2.00.1493.3188
X04=2.00.1493.3188
X05=2.00.1493.3188
X06=2.00.1493.3188
X07=2.00.1493.3188
X08=2.00.1493.3188
X09=2.00.1493.3188
X10=2.00.1493.3188
X11=2.00.1493.3188
X12=2.00.1493.3188
ZS1=2.00.1493.3188

[IDENT]
TYPE=Base Config File Type

 

[RodTrent]

Its going to be the site that is managing the client. The client will get the clicore information from the site that is managing it. Rod Trent
Microsoft.MVP.SMS
=======================================
Main site:

http://www.myITforum.com

=======================================

 

[snyderj]

The &quot;site supplying clicore&quot; will be the one that first updates that logon points with an updated clicore. If you have multiple child sites that are all supposed to be the same rev level then it's not too important which site goes first (though the parent is often the first site updated, but it may not be configured to have clients so it may not update the logon point).

 

[BobS53]

Thanks for the Reply.
I have 32 remote Site Servers, one of which is the Senior Site. Several of the Server locations have restrictions on what other servers they can see or have access too. For the most part each Site Server is it's own &quot;Mini&quot; domain due to firewall and network access restrictions. So What I'm trying to do is when there is a need to check or build new information, that Sitever.ini always points to my Senior Site (i.e XS1 Site Code). Some how, whenever that .ini is created on any workstation at any remote site, it always points to X28, which most User PCs and Site Servers do not have access too.