Log entries are as follows:
SMSClientMethodProvider log.
Failed to assign client to site. Error 80004005.
ClientLocation.log:
Unable to verify sitecode 001. Site assignment cannot continue.
LocationServices:
Failed to retrieve DND Service record using _smsmp_mp_001._tcp.domain.local
This is only when running a remote script. Running the script locally is fine,
as is changing the site code in the applet. The remote method is also used by
ClientCenter.
Anyway, this works but does spew out a few errors first in the
smsclientprovider.log.
$remoteHost = Read-Host -Prompt "Enter Hostname:"
$siteCode = Read-Host -Prompt "Enter Desired SiteCode:"
$mp = Read-Host -Prompt "Enter Default Management Point FQDN:"
$PSSession = New-PSSession -ComputerName $remoteHost
Enter-PSSession -Session $PSSession
Invoke-Command -Session $PSSession -InputObject $mp -ScriptBlock
{New-ItemProperty -path "HKLM:\SOFTWARE\Microsoft\CCM" -name "SMSSLP"
-PropertyType String -Force -value $input}
Invoke-Command -Session $PSSession -InputObject $siteCode -ScriptBlock
{([wmiclass]'root\ccm:sms_client').SetAssignedSite("$input")}
Exit-PSSession
Remove-PSSession -Session $PSSession
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im
Auftrag von Craig Andrew (OIZ)
Gesendet: Dienstag, 15. Oktober 2013 17:47
An: [email protected]
Betreff: AW: [mssms] Reassigning CM 12 clients
Will post the logs tomorrow. Basically the site cannot verify itself in AD when
the command is run remotely, but when changed through the applet it can. When
run locally, the command line works.
-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im
Auftrag von Jason Sandys
Gesendet: Dienstag, 15. Oktober 2013 17:33
An: [email protected]
Betreff: RE: [mssms] Reassigning CM 12 clients
Without looking at the logs, it's hard to say what was going on there, but
running a local script on the systems is no different than doing it in the
control panel to my knowledge. I guess it's possible it does something more,
but only the logs would confirm that. Definitely something to test though.
J
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Craig Andrew (OIZ)
Sent: Tuesday, October 15, 2013 10:24 AM
To: '[email protected]'
Subject: RE: [mssms] Reassigning CM 12 clients
I found that if you just reassign a client from the control panel applet then
it is ok, but when you do it remotely it would fail. Even though the AD is
correct.
However if you reassign the SMSSLP entry on the client first, then you can
remotely reassign no problem. The SMSSLP is no longer used in 2012, the role is
merged with the MP, but the entry in the registry remains. It may be that I had
the SMSSLP parameter in the initial install command line for the POC site
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Jason Sandys
Sent: Dienstag, 15. Oktober 2013 15:57
To: [email protected]
Subject: RE: [mssms] Reassigning CM 12 clients
In 2012, client can get the trusted root key from AD so assuming that they have
AD forest extended and you publish your site info in their forest, then you
just need to send out a script to reassign them.
J
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Brian McDonald
Sent: Tuesday, October 15, 2013 7:33 AM
To: [email protected]
Subject: [mssms] Reassigning CM 12 clients
Good morning,
We recently acquired a new company Who has deployed as SCCM 2012 already into
their environment. They have one primary site managing all clients. That would
be the best approach to reassign these clients to our corporate HQ primary site?
Thank you,
Brian
Sent from my iPhone
