How to change the site code

2009년 11월 24일 화요일 오후 7:49Felyjos

0
로그인하여 투표
Hello,

I am trying to move a Client from the site DTS to the site TST.
I have
- uninstall the previous Client
- delete the machine from DTS and TST
- discover the machine from the TST (Test) server
- the machine appear on TST after 5 minutes
- let the machine one day
- right click on the machine and try Install Client
also
- ran ccmsetup /Mp:configmgrtest smssitecode=tst

I see the ccmsetup running...
but after three days the machine is still pointing to DTS???

The boudries have been added on the TST test server and removed from DTS

I have the ccmsetup.log on the machine which looks good with the site code TST

quote:

MSI PROPERTIES are INSTALL="ALL" SMSSITECODE="TST" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" CCMFIRSTCERT="0" SMSPUBLICROOTKEY=0602000000A4000052534131000400000100010005C07A2BF73797FAACDDB
F3EC830CC471F88E675FF2D22E495264BB62A412DCE11118D8D61DBD5F3C5A4128CB08279DEFB3
E4092D0F966F49DF8253F5D38911C99B095F4700C9737DC1F965FAC29AD577A3705438B79CD71B0
B4B75DF2BE68C4A4A5F69C4229D94B3969DF3A64D88AD1149557490B324310AC5A43C0E52FA5C1 INSTALL=ALL

quote:

Installation succeeded.

but the smscliui.log shows still the old site DTS..

quote:

Current Assigned Site: DTS
Attempt to update the assigned site has failed. Error: 0X80040001
SMS Site code has not been changed. smscliui 11/23/2009 1:08:21 PM 2720 (0x0AA0)

but not in the Start > Control panel > Configuration Manager > General tab tghe managment point is still CONFIGMGRDTS the old server
in the Start > Control panel > Configuration Manager > Advanced tab it is still DTS the old site

I have
- uninstall the previous Client
- delete the machine from DTS and TST
- discover the machine from the TST (Test) server
- the machine appear on TST after 5 minutes
- ran ccmsetup /Mp:configmgrtest smssitecode=tst RESETKEYINFORMATION=TRUE

Waiting the end of ccmsetup process... + msiexec
same old site ... Any log to check for this issue?

quote:

PolicyAgent.log
Requesting policy from authority 'SMS:DTS' PolicyAgent_RequestAssignments 11/23/2009 1:54:37 PM 1972 (0x07B4)

ClientLocation.log
Setting Assigned Site ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Assigning client to site 'DTS' ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Getting Assigned Site ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Client is currently not assigned to any site ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Removing client site assignments ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Raising event:
instance of CCM_RemoteClient_Reassigned
{
DateTime = "20091123214422.826000+000";
LastAssignedSite = "";
NewAssignedSite = "DTS";
ProcessID = 4316;
ThreadID = 4940;
};
ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Client assigned to site 'DTS' ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Discover Default MP ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Site Code is DTS; Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU ClientLocation 11/23/2009 1:44:22 PM 4940 (0x134C)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>. ClientLocation 11/23/2009 1:46:47 PM 5936 (0x1730)

smscliui.log
Current Assigned Site: DTS smscliui 11/23/2009 1:54:16 PM 4808 (0x12C8)
Checking the ClientLocation.log it seems removing the old site but reassigning the same old site ...!!!
Should I reboot the Client?

Another try:
ccmsetup /uninstall -- done
ccmclean /all -- done
ccmdelcert -- done
reboot

Wait a night ( about 8 hours)
When I run ccmsetup /mp:configmgrtest smssitecode=TST RESETKEYINFORMATION=TRUE
Still going to the old DTS site...

One quick question:
- if the machine is out of boundaries but in OU structure of the old Server which is the order it will be treated...

Thanks,
Dom
Altiris Support / System Center Configuration Manager Support
- 편집됨Felyjos 2009년 11월 24일 화요일 오후 7:52
- 응답
- 인용

답변

2009년 11월 25일 수요일 오후 1:01John MarcumMVP, 중재자

1
로그인하여 투표
I generally don't run labs on the my live Active Directory, Ihave a complete offline AD and SCCM for my labs. I think what you have done here will work though. You should even be able to publish TST to AD so the client can be assigned. Are you sure there are not GPO's assigning the client to DTS? BTW... you mentioned you waited 3 days and the machine is still pointing to DST, that's by design. Clients will never reassign themselves you have to dothat manually or via a script. As Torsten said what happens when you try to discovery site code from the control panel?

Discovery has nothing to do with which site the machine is assigned to. DST is still discovering you client because it's in a OU that DST discovers. That will keep happening unless you move the client to an OU that DST isn't set to or doesn't have permission to discover.

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
- 답변으로 표시됨Jie-Feng Ren 2009년 12월 4일 금요일 오전 5:20
- 응답
- 인용

모든 응답

2009년 11월 24일 화요일 오후 7:51

Felyjos

로그인하여 투표

When I run the discovery on the new site TST the machine is discovered.
When I run ccmsetup /mp:configmgrtest smssitecode=TST RESETKEYINFORMATION=TRUE

it still going to the old site...

Waking up for site control file directory change notification	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
The Site Control File has not changed since the last parameter update.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Updating Site Parameters	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
MP Ports: 80	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
MP SSL Ports: 443	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
IISPreferedPort: 80	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
IISSSLPreferedPort: 443	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Default MP: CONFIGMGRTEST	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
SSL State: 0	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Certificate Selection Criteria:	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Certificate Store:	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Select First Certificate: 0	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Checking configuration information for server: CONFIGMGRTEST.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
No Fallback Status Point installed on the Site	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Install on DC: False	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Sleeping for 1200 seconds...	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:52:43 AM	4288 (0x10C0)
Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:12 AM	4468 (0x1174)
Received request: "ERDXTKGM" for machine name: "OPPMCCS6090A" on queue: "Incoming".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:12 AM	4468 (0x1174)
Stored request "ERDXTKGM", machine name "OPPMCCS6090A", in queue "Processing".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:12 AM	4468 (0x1174)
----- Started a new CCR processing thread. Thread ID is 0x40e4. There are now 1 processing threads	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	4468 (0x1174)
Submitted request successfully	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	4468 (0x1174)
======>Begin Processing request: "ERDXTKGM", machine name: "OPPMCCS6090A"	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	16612 (0x40E4)
Getting a new request from queue "Incoming" after 100 millisecond delay.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	4468 (0x1174)
Waiting for change in directory "C:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	4468 (0x1174)
---> Trying the 'best-shot' account which worked for previous CCRs (index = 0x0)	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	16612 (0x40E4)
---> Attempting to connect to administrative share '\\OPPMCCS6090A.ad.medctr.ucla.edu\admin$' using account 'AD\Dominiqued'	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:14 AM	16612 (0x40E4)
---> The 'best-shot' account has now succeeded 8 times and failed 0 times.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Connected to administrative share on machine OPPMCCS6090A.ad.medctr.ucla.edu using account 'AD\Dominiqued'	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Attempting to make IPC connection to share <\\OPPMCCS6090A.ad.medctr.ucla.edu\IPC$>	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Searching for SMSClientInstall.* under '\\OPPMCCS6090A.ad.medctr.ucla.edu\admin$\'	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> System OS version string "5.1.2600" converted to 5.10	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Service Pack version from machine "OPPMCCS6090A" is 3	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Unable to connect to WMI (r) on remote machine "OPPMCCS6090A", error = 0x8004100e.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Creating \ VerifyingCopying exsistance of destination directory \\OPPMCCS6090A\admin$\system32\ccmsetup.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:15 AM	16612 (0x40E4)
---> Copying client files to \\OPPMCCS6090A\admin$\system32\ccmsetup.	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:16 AM	16612 (0x40E4)
---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "\\OPPMCCS6090A\admin$\system32\ccmsetup\MobileClient.tcf"	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:16 AM	16612 (0x40E4)
---> Created service "ccmsetup" on machine "OPPMCCS6090A".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)
---> Started service "ccmsetup" on machine "OPPMCCS6090A".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)
---> Deleting SMS Client Install Lock File '\\OPPMCCS6090A.ad.medctr.ucla.edu\admin$\SMSClientInstall.TST'	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)
---> Completed request "ERDXTKGM", machine name "OPPMCCS6090A".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)
Deleted request "ERDXTKGM", machine name "OPPMCCS6090A"	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)
<======End request: "ERDXTKGM", machine name: "OPPMCCS6090A".	SMS_CLIENT_CONFIG_MANAGER	11/24/2009 11:53:17 AM	16612 (0x40E4)

Any idea?

Thanks
Dom

Altiris Support / System Center Configuration Manager Support

편집됨Felyjos 2009년 11월 24일 화요일 오후 7:58

2009년 11월 24일 화요일 오후 7:56Eirik Hamer

1
로그인하여 투표
Are both sites primary sites?
- 응답
- 인용

2009년 11월 24일 화요일 오후 7:59

Felyjos

로그인하여 투표

One is Test site on its own as Primary - Type: Primary - Parent Site : None , the other one is a Primary Child for Production - Type: Primary - Parent Site : MED

this the Client location.log on CONFIGMGRTEST !!!!

Setting Assigned Site	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Assigning client to site 'DTS'	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Getting Assigned Site	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Client is currently not assigned to any site	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Removing client site assignments	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Raising event:

instance of CCM_RemoteClient_Reassigned
{
	DateTime = "20091124195502.436000+000";
	LastAssignedSite = "";
	NewAssignedSite = "DTS";
	ProcessID = 5612;
	ThreadID = 3228;
};
	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Client assigned to site 'DTS'	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Discover Default MP	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Site Code is DTS; Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Setting Current Management Point	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU	ClientLocation	11/24/2009 11:55:02 AM	3228 (0x0C9C)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:55:03 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:55:03 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:55:03 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:55:03 AM	3228 (0x0C9C)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:55:03 AM	3228 (0x0C9C)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:55:03 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:55:03 AM	4828 (0x12DC)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:55:03 AM	4828 (0x12DC)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:55:03 AM	4828 (0x12DC)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:55:03 AM	4828 (0x12DC)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:03 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:03 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:06 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:07 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:07 AM	3072 (0x0C00)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:07 AM	3072 (0x0C00)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:07 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:08 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:08 AM	3172 (0x0C64)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:08 AM	3172 (0x0C64)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:08 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:08 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:09 AM	5992 (0x1768)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:09 AM	5992 (0x1768)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:09 AM	5992 (0x1768)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:09 AM	5316 (0x14C4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:09 AM	5316 (0x14C4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:09 AM	5992 (0x1768)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:09 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:09 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:11 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:11 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:11 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:11 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:11 AM	3072 (0x0C00)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:11 AM	3072 (0x0C00)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:56:13 AM	2532 (0x09E4)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:56:13 AM	2532 (0x09E4)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:58:14 AM	5240 (0x1478)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:58:14 AM	5240 (0x1478)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:58:16 AM	5120 (0x1400)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:58:16 AM	5120 (0x1400)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:58:25 AM	4992 (0x1380)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:58:25 AM	4992 (0x1380)
GetCurrentManagementPointEx	ClientLocation	11/24/2009 11:58:25 AM	4992 (0x1380)
Current Management Point is CONFIGMGRDTS.AD.MEDCTR.UCLA.EDU with version 6221 and capabilities: <Capabilities SchemaVersion="1.0">
</Capabilities>.	ClientLocation	11/24/2009 11:58:25 AM	4992 (0x1380)

Thanks,
DOm

Altiris Support / System Center Configuration Manager Support

2009년 11월 25일 수요일 오전 2:08John MarcumMVP, 중재자

1
로그인하여 투표
Both sites published to AD? Same boundaries on both sites?

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
- 응답
- 인용
2009년 11월 25일 수요일 오전 5:25Felyjos

0
로그인하여 투표

Both sites published to AD? Same boundaries on both sites?

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
Hello John,

1. No only the old site DTS has been published.
    The new site TST is a test site and has not been published. Should it be?

2. No the IPs are set by range and I checked again
   DTS has a range from 10.2.234.1 - 10.2.234.41 & 10.2.224.47 - 10.2.234.127
   TST has a range from 10.2.234.45 - 10.2.234.46

Anything wrong?

Thanks,
Dom
Altiris Support / System Center Configuration Manager Support
- 응답
- 인용
2009년 11월 25일 수요일 오전 7:38Torsten [MVP]MVP

1
로그인하여 투표
What happens if you would use the control panel to assign the client to TST?
- 응답
- 인용
2009년 11월 25일 수요일 오후 1:01John MarcumMVP, 중재자

1
로그인하여 투표
I generally don't run labs on the my live Active Directory, Ihave a complete offline AD and SCCM for my labs. I think what you have done here will work though. You should even be able to publish TST to AD so the client can be assigned. Are you sure there are not GPO's assigning the client to DTS? BTW... you mentioned you waited 3 days and the machine is still pointing to DST, that's by design. Clients will never reassign themselves you have to dothat manually or via a script. As Torsten said what happens when you try to discovery site code from the control panel?

Discovery has nothing to do with which site the machine is assigned to. DST is still discovering you client because it's in a OU that DST discovers. That will keep happening unless you move the client to an OU that DST isn't set to or doesn't have permission to discover.

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
- 답변으로 표시됨Jie-Feng Ren 2009년 12월 4일 금요일 오전 5:20
- 응답
- 인용
2009년 11월 25일 수요일 오후 4:29Felyjos

0
로그인하여 투표
What happens if you would use the control panel to assign the client to TST?

Failed to update site assignment
Altiris Support / System Center Configuration Manager Support
- 응답
- 인용
2009년 11월 25일 수요일 오후 4:33Felyjos

0
로그인하여 투표
I generally don't run labs on the my live Active Directory, Ihave a complete offline AD and SCCM for my labs. I think what you have done here will work though. You should even be able to publish TST to AD so the client can be assigned. Are you sure there are not GPO's assigning the client to DTS? BTW... you mentioned you waited 3 days and the machine is still pointing to DST, that's by design. Clients will never reassign themselves you have to dothat manually or via a script. As Torsten said what happens when you try to discovery site code from the control panel?

Discovery has nothing to do with which site the machine is assigned to. DST is still discovering you client because it's in a OU that DST discovers. That will keep happening unless you move the client to an OU that DST isn't set to or doesn't have permission to discover.

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

1. let let me try to move the machine out of the OU
2. Control Panel: Failed to update site assignment
3. I ran a script from one of you John or Torsten
```
Dim oSMSClient
Dim oUIResManager
Dim oUIResource


set oSMSClient = CreateObject ("Microsoft.SMS.Client")
set oUIResManager = createobject("UIResource.UIResourceMgr")
Set oUIResource = CreateObject("UIResource.UIResourceMgr")
Set objCacheInfo = oUIResource.GetCacheInfo
Set oCache=oUIResManager.GetCacheInfo()

if Err.Number <>0 then
wscript.echo "Could not create SMS Client Object - quitting"
end if

'Assign client to Servername
oSMSClient.SetAssignedSite "TST",0

set oSMSClient=nothing
```
and it affecred the TST site for sometimes so ...

4. Yes there are GPOs somewhere I need to verify this again

HAPPY THANKSGIVING

Thanks,
Dom
Altiris Support / System Center Configuration Manager Support
- 응답
- 인용
2009년 11월 25일 수요일 오후 8:14John MarcumMVP, 중재자

1
로그인하여 투표
If you ever assign a computer to a site using a GPO it tattoo's the registry and you can't just change the site code. You eithe rhave to chage it with a GPO or clean the registry.

Save this as a vbs and run it on the client then see if it will reassign:

OPTION EXPLICIT

DIM WshShell

On Error Resume Next

Set WshShell = WScript.CreateObject("WScript.Shell")

WshShell.RegDelete "HKLM\Software\Microsoft\SMS\Mobile Client\GPRequestedSiteAssignmentCode"
WshShell.RegDelete "HKLM\Software\Microsoft\SMS\Mobile Client\GPSiteAssignmentRetryDuration(Hour)"
WshShell.RegDelete "HKLM\Software\Microsoft\SMS\Mobile Client\GPSiteAssignmentRetryInterval(Min)"
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
- 응답
- 인용
2009년 11월 25일 수요일 오후 9:57Felyjos

0
로그인하여 투표
This vbs did not change the site code... so i changed it manually to TST HKLM\Software\Microsoft\SMS\Mobile Client\AssignedSiteCode
and run again the previous script which was updating the site code...

Let see how long it stays .. it seems staying longer waiting to see if it capture the info from the new site

Do I need to publish the TST site (new site) to make it works...?
The site code seems stable with TST on the local machine but no task is received so far... about 1 hour now...

I have only:
- Machine Policy Retrieval & Evaluation Cycle
- User Policy Retrieval & Evaluation Cycle

under the Actions Tab from Start > Control Panel > Configuration Manager on the local machine
I have verified the
- Hardware Inventory Client Agent
- Software Inventory Client Agent
- Advertised Program Client Agent
at least are enabled

And I clik "Initiate Action" on the Client side to try to get them populated ...

Thanks,
Dom
Altiris Support / System Center Configuration Manager Support
- 응답
- 인용
2009년 11월 25일 수요일 오후 11:28John MarcumMVP, 중재자

1
로그인하여 투표
The vbs I posted wasn't meant to change the site code, only to clean the registry so the auto detect site code would work.

John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
- 응답
- 인용
2009년 11월 25일 수요일 오후 11:39Felyjos

0
로그인하여 투표
No problem. it did not clean the registry.
The Keys
"HKLM\Software\Microsoft\SMS\Mobile Client\GPRequestedSiteAssignmentCode"
"HKLM\Software\Microsoft\SMS\Mobile Client\GPSiteAssignmentRetryDuration(Hour)"
"HKLM\Software\Microsoft\SMS\Mobile Client\GPSiteAssignmentRetryInterval(Min)"

do not exist as is...

"HKLM\Software\Microsoft\SMS\Mobile Client\SiteAssignmentCode" exists it is where I input "TST".

nothing else...

Thanks,
Dom

Altiris Support / System Center Configuration Manager Support
- 응답
- 인용