After renaming several machines on our network in prep for a large scale renaming, we've noticed that the machines do not recognize any maintenance windows applied to collections they are in. This causes them to install software and patches any time they feel like, usually rebooting when they are done with no notice. Machines in SCCM have updated their names by Heartbeat discovery already and there are no duplicate entries. Running the report "Maintenance Windows Available to a Particular Client" shows no windows assigned to any of these renamed machines, even though I can see them applied to the collection, and see the machines in the collection. This doesn't seem to affect any of the machines in the same collections that were not renamed. Does any one know how to correct this or why it's doing this? I have already tried manually kicking off Machine Policy Refresh and Discovery Data Collection Cycle on the machines. It's been 2 days since they were renamed and it hasn't corrected itself yet. Although I do have 2 other machines I renamed a week ago that have seemed to fix themselves. Thanks, any help would be greatly appreciated.

Hello - Why don't you try to delete the system record from console and reinitiate Data Discovery Cycle from control panel client applet?Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

The information will be updated in the console when the clients runs the next heartbeat discoveryKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

They have already been updated via Heartbeat as I stated in my post. I set my heartbeat to run every 2 hours while we are doing this. Everything gets updated except the maintenance window. Seems to be something with the server though. Since posting I've noticed a few of the machines did get the maintenance window updated in the server, even though the machine did not reflect it until I forced a machine policy refresh. But it seems sporadic and random. Before we rename the rest of our 2000 clients I want to make sure I can get this straightened out.

I finally figured it out. In the collection where the maintenance window is applied, the machines that are having issues are marked obsolete. This collection is populated using a query based on AD OU. They also have an active entry in the All Systems collection. Once I forced a System Group discovery and updated collection membership the new active entries where placed into the maintenance window collection and had the window applied. This didn't occur with every machine we renamed though, only with a handful. Weird that they all didn't have an obsolete entry. Thanks for those that replied, appreciate the assistance.