Hello everyone, I would like some thoughts on the following plan: 1. Currently running 18.104.22.168 on a blade server with 5700 nodes. CMA V22.214.171.1246, MASE 8.5, VSE 8.5i. Performance is crappy on the blade.
2. I would like to do a clean install of V4.0 on a full size server with a different name & ip address than the existing blade server, then migrate nodes site by site. I would check in the VSE products and then import the policies from the blade server.
3. How can I migrate nodes from the nodes from the old blade server (V126.96.36.199) to the new V4.0 server?
There's no tool that allows you to directly export the tree and then re-import. The easiest way around this is to run a report and/or query in 3.x that lists all of the nodes broken down by there they're at in the system tree. Then on the 4.0 system you'll need to create the systems using 'from text file' (there's good documentation on the text file in the PDFs).
The current 3.6 environment was setup by a consultant and does not use ip sorting. It sounds like I have to resort to your second option of switching out the sitelist.xml file on each node. hmmm sounds like a lot of work.
The other option I am considering is this: 1. power down the blade then pull it off the network. 2. Have a new full size server built but not on the network with the same name & IP of the blade. 3. On the new server install V3.6.1 along with patches, then check in VSE 8.0i , 8.5i, MASE 8.0 & 8.5 and CMA 188.8.131.526. 4. then import VSE 8.0 & 8.5i policies from the blade. 5. Then put the new full size server on the network & wait for everyone to check back in.
Unfortunately I cannot setup IP sorting due to vlans etc globally. I have been moving systems from the lost & found for the last year and a half.
I was part of the 4.0 beta project & did play with the tags somewhat. I understand that CMA V4.0 is needed for the 'is laptop' tag to be active. That will help as we break out our machines by type i.e. desktop & laptop.
So for now I am leaning either towards the script or the new build & then upgrade to V4.0.
Perhaps down the road in V4 I will get the automatic sort that is now missing.
Easiest way is to either (re)push the agent from the 4.0 server OR create an installation package on the new server and run it from an install script. You could also do a single pull in from AD and then push against the nodes that it brings in.