-
1. Re: how do you handle a scenario where that server you added was offline?
Joe Piotrowski Feb 24, 2014 12:08 AM (in response to Anirban Dutta)1 of 1 people found this helpfulWhat does "you added" mean? You bulk added servers to BL and some of the server were offline so the agent didn't add the server properties when they were enrolled? Or something was deployed to servers that were offline?
The question needs to be much more specific.
-
2. Re: how do you handle a scenario where that server you added was offline?
John Landells Feb 24, 2014 4:10 AM (in response to Anirban Dutta)Hi Anirban,
I agree with Joe Piotrowski that we need more information for a specific answer, however, something that I've implemented with many of my clients over the years is to create a Server Smart Group which shows all servers with OS equals "Unknown". This can then be used in many ways, for example it could be used as a target group for a Unified Installer Job.
This is a rather general method, and I'm not sure it really answers your question....!
God bless,
-John.
-
3. Re: how do you handle a scenario where that server you added was offline?
Pankaj Kumar Singh Feb 25, 2014 1:57 AM (in response to Anirban Dutta)Creating smart group of servers with live agent and executing deployment job on this smart group will help in making sure that deployment only happens on managed servers(Agent is alive)
-
4. Re: how do you handle a scenario where that server you added was offline?
Bill RobinsonFeb 25, 2014 6:33 AM (in response to Pankaj Kumar Singh)
not really - the 'agent is alive' property is populated by a usp job, so that's only going to be as good as the last usp run assuming the agent hasn't gone offline. jobs typically handle unavailable servers pretty well - eg, they show an error because a target is not available. also - imo you shouldn't exclude targets from a group based on online/offline. if a system needs to get patched or have something deployed, then you should know that the deploy did not happen.