I'm trying to upgrade CSA 18.104.22.168 to 5.2. The problem is that we have a couple hundred users with laptops that aren't going to be here until January. We have a rule in place that prevents users from modifying agent files and security level. It also prevents Altiris from pushing out the new version of CSA. I have since removed that rule but the users that aren't here haven't received the update. So when we upgrade the server to 5.2, they won't be able to get the update and therefore no upgrade. I've tried numerous things including setting up a mirror of the current server but the SSL CA's don't match and the new agents will not register to the new MC. So I tried to push out the new certs to the hosts (along with updated DNS to point to the new server). The rule that blocks the upgrade also blocks the new Certificate file from being copied. Is there anything I can do to get this working? I'm at a loss as to what to do now. Thanks for any help you can give.
I'm sorry to hear that 5.2 isn't on the production server and it may be too late to do a migration for all hosts because you can only migrate from previous versions of CSA.
I hope Cisco is listening: It would be nice to migrate same versions of CSA or at least install an agent kit to migrate to another MC from an existing MC!
You can replace the certificate on hosts but they also have to report to an MC with the same name and you must suspend security to do it.
Another option is for you to build your new MC on a production server. You could then at least migrate the hosts still reporting to the 5.0 MC.
On the 5.2 hosts you could uninstall the current agents and use your deployment software to install the new agent.
You'll need to keep the 5.0 MC running until you migrate all hosts off of it.