Has anyone seen any problems with agents of version 6.0.0.1 updating to 6.0.0.3?

I think it's tied into me removing the .root out of the bulk of my group names because I found it to clutter my already long machine group names. However when i check the default agent it claims the agents will check in to the group "unnamed.root" and that's cool. I have both an unnamed group with a sub group of root and root group with a sub group of unnamed. However the agents write to the error log "Agent offline - `Machine ID.Group ID` not recognized by the KServer' "

My check-in policy allows for groups and sub groups to be created as well since both options are checked

 Allow automatic account creation for selected Group ID  

 Allow automatic account creation for groups without a policy  

Then the agents go offline and never seem to check-in again. Wondering if anyone else may be running into this or have an idea that i'm simply overlooking?

check-in policy

root.root Auto Enabled	

                 21 days

                 30 days

root.unnamed Auto Enabled 

                 21 days

                 30 days

unnamed.root Auto Enabled	

                 21 days

                 30 days

unnamed.unnamed Auto Enabled	

                 21 days

                 30 days

Thanks ahead of time

Todd

Legacy Forum Name: Problems updating a few agents,
Legacy Posted By Username: tsorensen@group1auto.com