Hi All, Everything is running fine... Except one thing; I have some clients that still reside in a POC, and some clients in a Test environment. I just wanted to quickly reassign some clients from the POC to Prod and then have them rebuild to the current OS build. And I might want to reassign clients in the future from Test to Prod or vice versa.
Obviously not a frequently used script, but this should work: $siteCode = "001" $setSiteMethod = "SetAssignedSite" $wmiclass = [wmiclass]"\\notebook\root\ccm:sms_client" $inParamsAddEntry = $wmiclass.psbase.GetMethodParameters($setSiteMethod) $inParamsAddEntry.sSiteCode = $siteCode $wmiclass.psbase.InvokeMethod($setSiteMethod, $inParamsAddEntry, $null) And I get an 80004005 Error in the SMSClientMethodProvider log. Failed to assign client to site. I can run other methods remotely against this class. I can change the sitecode manually from the client. So I looked in the LocationServices and ClientLocation and found these errors: ClientLocation: Unable to verify sitecode 001. Site assignment cannot continue. LocationServices: Failed to retrieve DND Service record using _smsmp_mp_001._tcp.domain.local We have overlapping boundaries but they are only content boundary groups. No site assignment boundary groups. I tried nslookup on the service records and they are not found. All sites are set to publish to DNS. AD looks correct, proper rights on the container, objects created correctly. Clients install correctly in the TS and manually, although not using Client Push. I can manually create the service records, if I ask the DNS team nicely. Question is, are these service records only first created when a site assignment boundary group is created? The clients are ok, they have their site assignment stored locally, and changes to site assignment don't happen often. It's a single site so roaming is not a problem. But I don't like thinking that someone may not be quite right. EDIT: Have just tried the powershell locally and that works. I have checked WMI and DCOM permissions. Anyone seen this before? I am very confused now.... The above problem and errors are only when using either a remote invoke, or a remote pssession or indeed remote wbemtest... Thanks Andrew
