Hello, is there some way to change the MP the client points to after the client software is installed considering: SCCM Site Mode is MixedSCCM isn't published on Active Directory (schema wasn't extended)WINS isn't usedMP is published on DNS I already read Client's Management Point Assignment TechNet post but it doesn't answer to my question. Thank you, LucaDisclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Hi, You may refer to the following blog: Reassigning a Configuration Manager Client Across Hierarchies Regards, Sabrina

Hello, is there some way to change the MP the client points to after the client software is installed considering: SCCM Site Mode is MixedSCCM isn't published on Active Directory (schema wasn't extended)WINS isn't usedMP is published on DNS I already read Client's Management Point Assignment TechNet post but it doesn't answer to my question. Thank you, Luca Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. Hello, What do you want to do? Move your MP role to a new server? If you change your MP it will publish to DNS then clients will request DNS and will retrieve the new MP server name. Client use site code to query DNS and retrieve MPs, so no problem for me. Julien

Hello jdulongc, I haven't to move MP role, but I have some SCCM clients didn't register correctly (see screenshot below); Management Point entry is missing and both ConfigMgr Connection Type and Site Mode are Unknown. So is there a way to fix this without re-installing SCCM Client considering: SCCM Site Mode is MixedSCCM isn't published on Active Directory (schema wasn't extended)WINS isn't usedMP is published on DNS Thank you a lot. Luca Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Did you specify DNS suffix in Advanced tab? Because I think that you have to specify when you want to use MP DNS publishing. Julien

Hello Julien, if I try to discover it in Advanced tab, I get this error: Automatic site code discovery was unsuccessful. According to this TechNet article About Client Site Assignment in Configuration Manager => How Auto-Site Assignment Works: Configuration Manager 2007 clients that use auto-assignment attempt to find site boundaries published to Active Directory Domain Services. If this method fails (for example, the Active Directory schema is not extended for Configuration Manager 2007, or clients are not within the same forest), clients can find boundary information from a server locator point. ...and reading this other TechNet article Configuration Manager and Service Location (Site Information and Management Points) => Site Information: Server Locator Point: If you have not extended the Active Directory schema for either SMS 2003 or Configuration Manager 2007, clients can automatically find a server locator point if it is manually published in WINS and if clients have not been installed with the SMDDIRECTORYLOOKUP installation property. For more information about manually publishing the server locator point in WINS, see How to Manually Add Configuration Manager Site Information to WINS. ...As written on my post, AD Schema was not extended for Configuration Manager 2007 and WINS is not used. I fired to set Site Code by VBscript: Change sccm configmgr client site code but otherwise Management Point entry is missing and both ConfigMgr Connection Type and Site Mode are Unknown. So is there a way to set Management Point manually by script without re-installing client ? Thank you. Luca Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

Hello, You cannot use auto discover if you don't extend AD, or don't use SLP. You have to script to set your site code, and setup DNS suffix in order to find the MP. For the moment it doesn't find the MP because you didn't setup dns suffix in SCCM agent configuration (in advanced tab) http://technet.microsoft.com/en-us/library/bb632435.aspx http://technet.microsoft.com/en-us/library/bb633030.aspx