12/04/2009 3649 views
Under normal circumstances, Kace's solution to apply a backup from the applicance to the VM would be a slam dunk. However, we have a little more complicated situation to deal with.

Our appliance has been up and running for several years now and we have 5400 workstations checking in. We have applied the last server update last night, but we are holding off on distrubution of the new client pending a little testing. At this time, all of our workstations are at 4.3 or lower.

We implemented ssl on our applicance but we do not restrict access to ssl only. It is our plan to start updating all of our clients to 5.x in the next few weeks.

Due to changes in our network structure and implementing vmware on our server, matching the network for the vmserver to our appliances network is out of the question. We need to move to our new networking enviroment, which is where our vmserver is deployed.

The name for the kbox will differ which means there is a DNS issue to resolve. We will have to submit a different SSL cert for this virtual server, which will differ from what our clients have. The ip for the vkbox will be different also.

Have any of you had to deal with these circumstances?

0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

When you you restore the backup's to the new the vkbox it will autoconfig the network settings to match. maybe a gpo to replace the conifg.xml file, and snnp.conf files with the new information?
Answered 12/04/2009 by: dtuttle
Purple Belt

Keeping the FQDN name the same would be ideal.

Otherwise, if there is a period of time where you can have both servers up then you could sript a change to tell the agents where to connect to next time. If so then this FAQ should still apply to you.

Make sure to test first
Answered 12/06/2009 by: GillySpy
7th Degree Black Belt