截屏视频帮助

Best practices for update testing

创建时间: 14 12 月 2012 • Updated: 09 1 月 2013 | 2 条评论
此问题已解决。 请查看解决方案。

I'm curious how folks are testing updates before applying to the production environment. I'm looking at applying the MP1.1 upgrade to 7.1SP2.

We have a single NS with 11 task and package servers.

My initial approach to testing was to convert the NS to a VM and bring it into an "on host" only network with VMWare. I was going to put SQL on the same VM and load the data from a backup. Then apply the updates and see what happens.

Some struggles are around the network access. The VM needs to have some access to pull the packages from Symantec, but will the NS also try to reach out to the production site servers since it's a clone of the production box? Will this cause problems if it does?

How are you building as accurate a test environment as possible to test updates?

Thanks for any feedback.

评论 条评论跳转至最新评论

andykn101 的图片

Test environments for Altiris are almost impossible to do realistically. Once in production I usually recommend another server in the production environment, in the same AD OU. I have onboard MSDN/Technet SQL with Analysis and Reporting for IT Analytics and just restore a backup of the Prod database whenever I want to test an upgrade. If Deployment is being used use a seperate VLAN.

To get the Executables in an environment not internet coeected use the "Create Install Pacakge" option in Symantec Installation Manager.

The only thing the test NS is likely to do in a production environment is the scheduled push of agents to computers it thinks haven't an agent or Network Discovery if you've got any of those set up.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

解决方案
aschuler 的图片

Okay, thanks for that. I guess maybe I'll go the route of a test server with a cloned database instead of trying to do a full clone of the NS.

Thanks.