Hi, What does Approved "N/A" mean for a client? Is the computer/agent considered ok/everything is working? I have seen that some clients has been a set to pproved and some to N/A, even if it is in the same boundary and domain. /Mikael

N/A means that approval is not applicable for this system. I've seen that for the following cases: * SMS 2003 clients - they are not subject to approval, so always N/A * Discovered systems that are not clients - we can't approve non-clients * Clients in native mode - no approval If these are Configuration Manager clients (in mixed mode), then they are still functioning normally, even if not approved. The only thing they can't do is use the Network Access account.

Dear Wally; I have the same problem. our configuration is: - All clients are in mixed mode. - All clients are in the same domain - We have 11 different subnets ( in different areas of the same country) - We have only one SCCM 2007 server SCCM 2007 clients was installed successfuly for all clients. but approved only for clients on the main office and just on a very little number of clients on other subnets. the approval setting is the default one. I also don't have the option to manually approve Non-Approved clients. How to approve these clients? Regards; Omari

You select the clients in a collection and then click Approve. That option is available on the Actions menu, with a right-click, and also in the Actions pane. http://technet.microsoft.com/en-us/library/bb633214.aspx

I know well how to approve clients in SCCM 2007, but what I want to say is that the option to approve is totally unavailable. (Exactly like when the client is not installed). Can I approve these clients using certain command line or script?

If the option to approve is not there, then the only reason I would know is that the systems: * Are not listed as Client = Yes * Are SMS 2003 clients * Are installed in native mode Unless there is something in the SDK, we don't have a script to automatically approve clients.

It's very likely that they aren't approved because they haven't registered. They could show up because they were discovered, or had clients at one time. The UI is actually pretty smart about whether or not you can "Approve" a client. You can approve through the SDK, but I'm not aware of any published scripts to do this.

My Clients are not listed as =Yes ( I need to know why is so as all the clients are trusted ones, single domain and client installation done well) Are SMS2007 clients Are installed in mixed mode

As mentioned in numerous other posts in this forum, you need to check in the logs. Here are the logs you should check assuming the client has been successfully installed locally: * 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

Hello,my client isnt in the domain but in the subnet. I can ping the client but approved is N/A. In the ClientIDManagerStartup.log I have following error: Code Snippet <![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="06:47:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"><![LOG[RegTask: Client is not registered. Sending registration request...]LOG]!><time="08:55:17.531+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="1" thread="3308" file="regtask.cpp:1434"><![LOG[RegTask: Failed to send registration request message. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1139"><![LOG[RegTask: Failed to send registration request. Error: 0x8000000a]LOG]!><time="08:55:17.546+420" date="07-25-2008" component="ClientIDManagerStartup" context="" type="3" thread="3308" file="regtask.cpp:1314"> How can I registrate the client?Thanks for your help.Argre

It happens automatically, and only at install time. We also retry the registration. The only way to force it, outside of our automatic retry, is to reinstall the client.

Thank you very much for your answer.I reinstalled the (workgroup-)client manually and the ccmsetup.log tells me that everything is ok: Code Snippet <![LOG[Installation succeeded.]LOG]!><time="13:06:37.578+420" date="07-28-2008" component="ccmsetup" context="" type="1" thread="3436" file="msiutil.cpp:890">In the Collection All Systems in the Configuration Manager Console there is still "No Client" and Approved is still N/A. It is assigned but it always was. So ... nothing changed.Thanks for your help!Argre my new Accountname: cm_home

In my last post (from Argre - today) I mentioned that the manual Client installation on a separate machine worked without problems but in the Configuration Manager Console the computer is still "N/A" in the Approved column and in the column "Client" there's still "No".It's important for me to know how to change the Approved Status from "N/A" to "Not Approved". (To change it from "not approved" to "approved" is quiet easy.) How to say the Configuration Manager Console that this Computer is a "good one" (with an already installed client)?Thank you for any helpful answer!cm_home

Hello all Had the same problem and I found a workaround. I have in place 16 primary sites (W2K3/SP2-SCCM 2007/SP1) and around 3500 clients. In my central site (mixed mode) around 1100 appeared as approval n/a. My setting regarding approval is to automatically approve all computers. Changed that to manuall approval, reboot central site server and then from the 1100 computers around three appear as n/a. Changed back the approval setting as it was and everything appears ok. The last three copmuters though still remain as n/a...Hope that helps.

Hello!Thank you for your reply but your workaround didn't fix my problem. But now I solved it. My idea that some components for the client were missing was correct but nobody could help me fo find the answer. I found a workaround and it works fine in my testing environment. I don't know if all of the "prerequisites" I'm installing are really necassary but it works.I have a new installation of the MS Windows 2003 Server R2.Then I install the Microsoft Deployment Toolkit,activate the IIS, BITS, WebDAV, SNMP and WINS within the system components,set BITS startup type to manually,edit the SNMP Service Properties Traps and Security,use the machines IP address for the WINS address,and import an corresponding LMHOSTS file.When completed all these tasks I start to install the SCCM client. After the restart I wait some minutes and then perform a "Update Collection Membership". - Voila!I hope I this post helps to solve some of your problems with the SCCM client.chrisps: Problems exist to be solved!

Hi.We are seeing the same issue on approximately 1% of our SCCM client installs so far. Our environment is Mixed mode. All clients are Windows XP SP2. We have 'Automatically approve in trusted domains' selected for our Approval mode.I have reviewed the client logs as suggested by Wally: clientlocationlog - client is assigned to a site locationservices.log - client has discovered default MP for the assigned site (and proxy MP) clientidmanagerstartup.log - I don't see any errors in this log and it appears that the client thinks it is registered (see snippet below)==================================RegTask - Executing registration task synchronously. ClientIDManagerStartup 12/15/2008 8:15:57 AM 3104 (0x0C20)Reg Task: Client is registered, exiting. ClientIDManagerStartup 12/15/2008 8:15:57 AM 3104 (0x0C20)Read SMBIOS (encoded): 3900390033004700390058003300 ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)Evaluated SMBIOS (encoded): 3900390033004700390058003300 ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)No SMBIOS Changed ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)SMBIOS unchanged ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)SID unchanged ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)HWID unchanged ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)Computed HardwareID=2:F64E8C91BC6B8979E11A5B8336243686E0697CD0Win32_SystemEnclosure.SerialNumber=Not AvailableWin32_SystemEnclosure.SMBIOSAssetTag=No Asset InformationWin32_BaseBoard.SerialNumber=J1UBT3CP1SFWin32_BIOS.SerialNumber=993G9X3Win32_NetworkAdapterConfiguration.MACAddress=<Not used on laptop> ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20)Persisted hardware IDs in CCM_ClientIdentificationInformation=@:HardwareID1=2:F64E8C91BC6B8979E11A5B8336243686E0697CD0HardwareID2=150E7B03016000DC ClientIDManagerStartup 12/15/2008 8:15:58 AM 3104 (0x0C20) ========================ccmexec.log - no issues communicating with MPDoes anyone have suggestions other than reinstalling the clients? We are just in client deployment right now and I'm wondering if this is something we're going to have to monitor on an ongoing basis. Thanks! Karen

Hi,Sorry to resurrect this thread but I'm seeing exact same problem on 3-5% of all our clients. The SP2 client is installed but clients show up as N/A in the console.Any ideas?

We ended up creating a collection for clients that were in Approved, N/A status. We monitor the collection and generally just approve all clients in the collection. We've seen no issues on the client side and still are unsure why some clients get this status.

@Karen H_ How did you create your collection for this? Can you reply withthe query which the collection is generated from, I am struggling to find the query which has the "IsApproved" in. I can do an SQL query to get this info, but it would be nice to have a collection with only these clients in.Cheers

Sure.Below is the query rule we used. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceId in (select sys.resourceid from sms_cm_res_coll_SMS00001 AS coll, sms_r_system as sys where sys.resourceid = coll.resourceid AND coll.isApproved = 2) and SMS_R_System.Client = 1

Brilliant, thanks for that!

In am having the same issue i have installed SCCM R2 in test environment in mixed mode, if have 300 clients but i am only able to install and approve 40 clients. All the clients are on XP SP3. Firewall is disable on all the clients. Please help me out i have already tried all the above suggestions.

Are you saying they are N/A? If so just ignore it? John Marcum | http://myitforum.com/cs2/blogs/jmarcum |

FYI: I created this collection which shows all clients which have the client installed, but are set to N/A or Not Approved. I can then choose which ones I want to approve... select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where (SMS_R_System.ResourceId in (select sys.resourceid from sms_cm_res_coll_SMS00001 AS coll, sms_r_system as sys where sys.resourceid = coll.resourceid AND coll.isApproved = 0) or SMS_R_System.ResourceId in (select sys.resourceid from sms_cm_res_coll_SMS00001 AS coll, sms_r_system as sys where sys.resourceid = coll.resourceid AND coll.isApproved = 2)) and SMS_R_System.Client = 1