Altiris 7.1 migration, Day 3
A few days in to the migration, have some questions came up. So lets go through it.
Our infrustructure is more like 1 huge building than 80 separate sites. The availability of having fiber connected to all the sattalite campuses means we can centrally manage as if they were in the same building. The problem is SMP isnt really designed for that kind of infrustructure. And the few issues we encountered are:
1. The technicians cannot manage the infrustructure in real time from 1 console. The amount of our clients meant we had to use hierchy, which means teh Parent server sees things later(Synch schedule). While all synched machines will be on the Parent server, any new clients will take 24 hours for the Parent console to see. Which means no OOB deployment from the parent Console.
2. Replication of packages maybe required as Task Servers, which means we would have to replicate our packages atleast 5 times(5 Task Servers). We dont need that as our San can handle the biggest deployments in the past with no issues for all clients accessing that one file share. replicating this 5 times will be expensive and over kill.
3. Big pain cleaning 6.x agent. If there are any reminents, the 7.1 agent ignores some of the install configurations. For example, it will install to C: instead of D: on the servers causing obvious issues.
Other than that, with Symantec poaching Altiris Administrators from the area, I dont have too many people to bounce ideas off of any more. Not the best start, but atleast all servers are up and running, just alot of tweaking and pilot to go through now.
Next week, DS and HII imaging, Software Library, and Agent deploy to Pilot Campuses.