You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A recent incident at my work occurred - were an individual deleted an OU without moving the computer objects out of that OU first.
All of those computer objects were deleted, therefore people could not log into those computers, could not access files and so on.
Can the FOG Client detect if the computer's Active Directory object exists or not - if the local computer says it's bound to a domain or not, and then check the FOG DB to see what it says about the situation?
For instance - if the fog client sees that the FOG DB says the host should be joined to the domain - and the client sees that the host says it's joined to the domain - but there is no AD Object for this particular host - to just go head and play "clean up", and just remove the host from the domain and then rejoin the domain.
THIS FEATURE would also assure that Active Directory computer objects are named correctly, I believe - depending on how the Active Directory query for the host is performed. Ideally, the search is performed using the hostname.
Thank you for giving FOG a new client,
Wayne
The text was updated successfully, but these errors were encountered:
A recent incident at my work occurred - were an individual deleted an OU without moving the computer objects out of that OU first.
All of those computer objects were deleted, therefore people could not log into those computers, could not access files and so on.
Can the FOG Client detect if the computer's Active Directory object exists or not - if the local computer says it's bound to a domain or not, and then check the FOG DB to see what it says about the situation?
For instance - if the fog client sees that the FOG DB says the host should be joined to the domain - and the client sees that the host says it's joined to the domain - but there is no AD Object for this particular host - to just go head and play "clean up", and just remove the host from the domain and then rejoin the domain.
THIS FEATURE would also assure that Active Directory computer objects are named correctly, I believe - depending on how the Active Directory query for the host is performed. Ideally, the search is performed using the hostname.
Thank you for giving FOG a new client,
Wayne
The text was updated successfully, but these errors were encountered: