I have SCCM 2007 R3 and I'm trying to install FEP onto our Citrix servers. Problem is that the servers don't show up in the collections. In our AD I've created security groups that I've been using for pushing out FEP (when I want someone to have it I add them to the appropriate group). I just added the Citrix servers to a group, but they don't show up. I have other VM's that show, but none of my Citrix servers. They are all provisioned, I don't know if that makes any difference. I have tried running both the "Active directory System Group Discovery" and the "Active Directory Security Group Discovery" to try and force them to be seen, but it has not worked. They are in a separate group from the others (but under the same OU) and I added a computer that I new would work just to make sure that the group is being discovered. the collection now shows only that one computer. Any ideas what the problem is?Mike in IT

Is SMS agent installed on those servers.Mayur

Neither of those discoveries actually discover resources. You ned to first run AD System Discovery.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

I have run the AD System Discovery, manually and allowing the schedule to run it last night. The servers still do not show up.Mike in IT

Is SMS agent installed on those servers. Mayur What SMS agent are you referring to? If I can't see them in the collections list how would I get the agent on them?Mike in IT

Have you reviewed adsysdis.log and searched for those systems? To be discovered, a system must have an account in AD, in an OU configured in the discovery, the acocunt must be enabled, and the system must be resolvable using DNS.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys

Have you reviewed adsysdis.log and searched for those systems? To be discovered, a system must have an account in AD, in an OU configured in the discovery, the acocunt must be enabled, and the system must be resolvable using DNS. Jason | http://blog.configmgrftw.com | Twitter @JasonSandys I've checked the log and they are not in it. These are VM's that we've been using for quite some time. the accounts are enabled the discovery is for the entire network. DNS look up works for all of them.Mike in IT

I got it to work halfway. I added the 2 security groups that they are in to the discoveries, individually. This picked up most of the VM's, but there are still 4 that are not showing even though they are in the same groups in AD. Why is it that the discovery will work for the whole of AD for the computers and physical servers, but wouldn't work for the VM's?Mike in IT

Is the OU in which those machines reside able to be read by the CM Server's computer account? If AD permissions are locked down... fyi, AD System Discovery, and client push is just one way to get the CM Client installed on computers. There are several other methods to install the client. Maybe client push just isn't the right way to get the CM Client installed onto these specific machines.Standardize. Simplify. Automate.

The CM client is already installed. My manager did that when he was setting up the SCCM server. I'm trying to install FEP. As to the first part, there are other VM's that are in the OU that show up in the collections, so the CM server has the permissions necessary to read what's in it.Mike in IT

"CM client is already installed"? What site code is it assigned to when you go to that machine's Control Panel applet, and look? What do the local logs for that client say?Standardize. Simplify. Automate.

Where would I find the Control Panel Applet? and where are the local logs I'm looking for?Mike in IT

On that citrix server, Control Panel. double-click Configuration Manager, Advanced tab. In general, the cm client log files are in %windir%\ccm\logs. But if we are talking cm07, AND that particular client happens to be x64, then they would likely be in %windir%\syswow64\ccm\logs.Standardize. Simplify. Automate.

Looks like I was wrong they do not have the CM client installed. I went ahead and pushed it out to the ones that show up, how else can I insure that they all get the client?Mike in IT

lol, that's a question many people face! Well, what's the summary of the situation now? i.e., what's left as issues you are currently facing?Standardize. Simplify. Automate.

Well, even though they don't have the client some of them are showing up in the collections, I still need the others to show up. That way once they have the client I can install FEP. There is a security group that has about 8 servers in it, only 5 are showing in the collection. The only difference between them is their names, they are provisioned servers.Mike in IT

For fun, forget the console for this. Launch SQL Management Studio, connect to the sql db, and create a new adhoc sql query, pointing to SMS_YourDB, and execute it. select * from v_r_system where netbios_name0 in ('Server1','Server2','Server3') see if those 3 are in the db...just not in the collection you are looking at. Oh, another thought... "provisioned servers"... provisioned how? If perhaps that group pre-loaded the ConfigMgr client on a template server, and then cloned it over and over again; that can mess with the CM Client on the duplicates; because the console doesn't treat them uniquely, it's the same "UniqueIdentifier" for each one (i.e., no longer really unique, because of the cloning). Standardize. Simplify. Automate.

The SQL query didn't come up with anything either. I'll have to talk to the guys who manage those servers and see about how they are duplicated. That idea about them not have UID's that are truly unique might just be the problem. I'll let you know what I find out, it probably won't be till next week though.Mike in IT

as I mentioned, it's just a theory. But if you want to pursue the duplicate theory, here's a link with some info to help you check to see if it is potentially the cause: http://elmunjo.blogspot.com/2010/01/managing-conflicting-records-and.html There's lots of other blogs and guides out there for dealing with duplicate guids, now that you know that's the term used, I'm sure you can track down all kinds of articles or guidance, to see if that may be your issue. Standardize. Simplify. Automate.

Okay, I spoke with my boss, he's the one who creates the VM's, they all have unique ID's. I just found out however that 4 of them are not turned on, I don't know if that makes a difference, and one is on. So even if being off means that they won't show, why won't the one that is on show up?Mike in IT

I don't know your environment, so I can't say "why doesn't one show up". Can you log into that one? Does it have the 'configuration manager' applet in control panel? Does it have a site code? If you have it locally do a heartbeat, what do it's local logs say? If you have it locally do policy refresh, what do the logs say? If you have it do inventory, what do local logs say? If after any of that, what do the Management Point logs say like the mp_ logs? If after hardware inventory, do you see the hinv process through dataldr.log on the server? I can't say what may or may not be the problem, as to why 1 specific box isn't showing up in your console--look at the logs. the logs will tell you everything. Of course, there are like 240 log files or something... :)Standardize. Simplify. Automate.

It is showing up now, I don't know exactly what changed. I do know that it has been restarted several times. Thanks for the help.Mike in IT