Client Manual Approval

[Centaur63]

I am having trouble trying to figure out how to approve my clients. As it stands right now they have N/A for approved. When I right click the client i do not see the approve option. I am in the All System Collection if that helps at all. I attached a screen sho tof what i am looking at. Any help with this would be great. Thanks again for any help or suggestions you can give me.

[Centaur63]

http://cid-339f51e91e743385.photos.live.com/self.aspx/Support/sccm.GIF

 

sorry that is the link of what i am seeing

[Eswar Koneti]

http://cid-339f51e91...upport/sccm.GIF

 

sorry that is the link of what i am seeing

 

N/A means that approval is not applicable for this system .

Are the machines with SMS 2003 client or SCCM Client Installed ?

 

For SMS 2003 clients - they are not subject to approval, so always N/A

If systems are discovered that are not SCCM clients - we can't approve non-clients

If Clients are in native mode - no approval.

Check the client log files to see what went wrong if SCCM client is installed.

ClientLocation.log to see if the client has been assigned to a site

* LocationServices.log to see if the client has discovered the default MP for the assigned site

* ClientIDManagerStartup.log to see if the client has registered properly

* Ccmexec.log to see if the client is having any issues communicating with the MP

http://technet.microsoft.com/en-us/library/bb633214.aspx

 

[Centaur63]

N/A means that approval is not applicable for this system .

Are the machines with SMS 2003 client or SCCM Client Installed ?

 

For SMS 2003 clients - they are not subject to approval, so always N/A

If systems are discovered that are not SCCM clients - we can't approve non-clients

If Clients are in native mode - no approval.

Check the client log files to see what went wrong if SCCM client is installed.

ClientLocation.log to see if the client has been assigned to a site

* LocationServices.log to see if the client has discovered the default MP for the assigned site

* ClientIDManagerStartup.log to see if the client has registered properly

* Ccmexec.log to see if the client is having any issues communicating with the MP

http://technet.microsoft.com/en-us/library/bb633214.aspx

 

 

I think i may have found the problem. The MP is set to the wrong Server. It is set to the one that has died. How can i fix that?

[Eswar Koneti]

I think i may have found the problem. The MP is set to the wrong Server. It is set to the one that has died. How can i fix that?

 

 

You can uninstall/Remove the MP role from the Current SCCM site which was pointing to wrong server and install the New MP role by providing the SCCM site server name.

[Centaur63]

You can uninstall/Remove the MP role from the Current SCCM site which was pointing to wrong server and install the New MP role by providing the SCCM site server name.

 

That seemed to work. Thanks alot for your help