Package Deployer : cliënts keep showing up in Unassigned group

Question

Hi All, 
 We have a SEC running and we use the package deployment tool to distribute the installations. Installations are containing RMS and configured to point to a specific group. At this moment we are experiencing problems with this functionality as new clients are Always showing up in the unassigned group. Even though we are sure the package deployer settings for additional properties is setup the correct way! It has been working before. 
 Has anyone a hint on where to start troubleshouting? 
 Thank you in advance. 
 Mark

QC · Accepted Answer

Hello Mark, 
 [note: if one is subscribed to a thread he or she receives a notification of all replies/appends - but thanks for keeping me in mind] 
 First of all, an installation of SDP is independent from SEC or its version (you can run SDP on any -Windows- machine, it only has to be able to access the required CID). If the -g is not in the .vbs then it was SDP's deed. Can't say why the minus/hyphen wasn't one but I'm pretty sure this was the cause. I've run SDP literally dozens of times and as far as I can see the logic is simple and while it is not absolutely flawless it doesn't drop a token starting with a hyphen. Anyway you can always check the resulting VBS if you are paranoid [;)]. 
 Whenever the Sophos Agent service starts it checks for the existence of the GroupPath value and if present it sends the respective message to the management server and deletes the value. The Agent is installed as part of RMS which is the first component that AutoUpdate installs on a managed endpoint. Can't recall that it'd require a reboot though. 
 but the GroupPath key is not read is the Sophos Agent service started? As said, it should always check during start-up (as Moving a computer ... describes), if not there's something not working as it should and this'd be a case for trace logging (not that I think you'd need it). 
 Christian