Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Upgrade
Showing posts in English
jjesse | 06 Apr 2009 | 2 comments

When you are ready to migrate to NS7 there are two options or ways to make sure all of your NS6 agents upgrade correctly to NS7. I'll discuss breifly two options and which one I believe is the cleaner and easier method.
When discussing the update of the client agents I ask one question:  Do you have the DS Agent installed on the client?  In the second way to upgrade the agent I'll discuss why I ask that question.
The recommend way to upgrade your agents from Symantec is to first enable the unistall agent policies for each subagent (not the main Altiris Agent) on the NS6 box and wait for the clients to check in, get the new policies and then remove those subagents. While those agents uninstall, make sure the Upgrade Agent policiy is enabled on the NS7 system.  Once the subagents are uninstalled, Inventory, Software Delivery, Patch, etc, then on the NS6 box change the Altiris Agent policy to point to an alternate NS, being the NS7 system. ...

rbrucelee1978 | 19 Mar 2009 | 0 comments

I have noticed that most of the links to sites "designed to help beginners" generally talk about how to create msi's, how to modify these packages or even how to fix some ICE errors. However, these sites do not give beginners any information on very important basic concepts such as Self Healing, Installation Sequences, how to read the logs generated on installation of the msi. These "basic" concepts can help beginners understand things like how these ICE errors occur or say in the even of a failed msi installation where to look in the package based on the information given by the verbose log file.

This site (written by John McFadyen) will provide detailed information on these concepts Windows Installer Blog.

Happy reading!! :-)

BRING | 14 Jan 2009 | 0 comments

Upgrades can be a challenging event, especially where there are multiple servers and groups affected and involved.

After a recent upgrade from Recovery Solution 6.2.2106 to 6.2.2760, testing was being performed to validate the usability of the upgrade.

While attempting to run the Recovery Agent Installation and configuration pages remotely, a "Internal Server Error" message was displayed, and further defined as a 500 level Internet Explorer error.

Accurately verifying the upgrade prerequisites ended up being a critical component here. A detailed examination of IIS showed that .NET was not installed and registered correctly, as there were default document references in IIS missing, such as default.aspx, and many cached ISAPI extensions were not present. Also, some NTFS permissions appears to be incorrectly set in the virtual...

haim96 | 09 Jan 2009 | 2 comments

Smart UAC is a clever program developed by Security Stronghold company which automatically replaces UAC (User Account Control) from Windows Vista with a much more powerful and intellectual one.

Unlike standard UAC, Smart UAC Replacement will not disturb you with numerous alerts of the good programs you use everyday over and over again. Smart UAC remembers your choice for a given program and will allow or deny it automatically unless you haven't changed your mind or unless the program's executable has changed.

The second great thing about Smart UAC is that it has a large and regularly updated database of more than 400,000 known threats including viruses, trojans, spyware, adware, keyloggers, privacy breakers and even rootkits. Smart UAC will scan each run program and automatically determine in milliseconds if it is known malicious program...

wuzfuzzy | 07 Nov 2008 | 5 comments

Is your organization moving from Novell Imaging to using ONLY Altiris DS? Did your organization use Image safe data during imaging? Are you still going to have Novell Client / Agent in in POST Altiris world? If you answer yes to all of these questions you will need to have a way to remove the image safe data. In the Novell world you would simply add a line to your linux script to call zisedit -c or zisedit -r and this would clean out the image safe data. But since you are now imaging with DS, this cannot be done directly in Altiris.

So after some Google searching I have found a very simple tool called ZisdCtrl from a company named Expert Networking Group Limited http://www.engl.co.uk With this tool and a simple script you can do the following:

  1. ...
piyushnasa | 22 Oct 2008 | 0 comments

In any of these installation transactions, viz. initial installation, repair, reinstallation, on-demand installation or patching an MSI, The REINSTALLMODE has an affect on it.

Here is what "amus" means:

  • a - Force all files to be reinstalled, regardless of version
  • m - Rewrite all registry keys that go to HKEY_LOCAL_MACHINE or HKEY_CLASSES_ROOT
  • u - Rewrite all registry keys that go to HKEY_CURRENT_USER or HKEY_USERS
  • s - Reinstall shortcuts and icons

The mentioning of "a" in amus forces the reinstallation of files on your machine irrespective of the file version rules. Every file updated by REINSTALL property will be updated in this case.

The sequence of events which happen actually depend on the authoring of your patch.

If your patch contains the full file, the installer will...

piyushnasa | 02 Sep 2008 | 0 comments

Are you facing a problem of failed uninstallation in your machine. Here is a tip to get it fixed.

When your MSI fails to uninstall because of an error or maybe because you have wrongly put a Custom Action to run at uninstall and it is failing. Even if you fix the error in your MSI by rebuilding it and try to install again, it will not work. This is because the maintenance mode will continue to use the cached version of MSI at Windows\Installer folder.

Many packaging people will suggest you to use third party utility like MSIZAP to completely remove the MSI. Though I won't say that's a bad option, but if we can make it work our MSI, that's preferable.

Here is what you need to do:

Fix the error in your package and set the REINSTALLMODE property to 'vomus'.

This will ensure it will run from the source package and re-cache the local package.

nac | 22 Aug 2008 | 1 comment

Well this is an intresting tip while moving from XP to Vista. When we launch the Help file in Vista, Help file (.hlp) may give you the following types of errors.

  1. An error like this means the particular Help file is not compatible to work on Vista. You need to apply a Help patch. So unless and until you apply a patch you will not be able to open the Help file.

    You can download this patch from following link.

    http://www.microsoft.com/downloads/details.aspx?Fa...

  2. It doesn't stop there. After applying the patch you open Help again and this time you may...
Dan Waksman | 20 Aug 2008 | 3 comments

If you are beginning to test Vista, and are looking into the various activation methods, you will quickly learn that KMS activation requires a minimum of 25 PCs. Therefore you may need to begin testing with a MAK key and later switch to activating against a KMS server.

In order to switch back to KMS activation, use the following command lines for Vista Enterprise:

slmgr.vbs /ipk VKK3X-68KWM-X2YGT-QR4M6-4BWMV
slmgr.vbs /skms SERVERNAME
slmgr.vbs /ato

For Vista Business, substitute the key with YFKBB-PQJJV-G996G-VWGXY-2V3X8. See http://technet.microsoft.com/en-us/library/cc30328... for more details on Volume Activation 2.0.

If you need to switch back to a MAK key,...

Dan Waksman | 06 Aug 2008 | 1 comment

If you have created a Vista image using a Scripted OS Install task, then you most likely left the command line to install the DAgent: C:\DAgent\DAgent.msi /quiet server_tcp_addr=%DSSERVER% server_tcp_port=402 scripted_install=1 LAUNCHUI=FALSE

However, you have now created an image that will connect the DAgent to whatever Deployment Server the image was created on. If you are using multiple Deployment Servers and are trying to use the same image, obviously this will be an issue. To work around this, I created a task to run immediately after a Distribute Image Task in WinPE pre-boot automation, which switches the DAgent to the correct Deployment Server, by modifying the registry:

REM Point DAgent to correct DS

reg load HKLM\TEMP c:\windows\system32\config\software
reg add "HKLM\TEMP\Altiris\Client Service" /v DSIp /t REG_SZ /d "%...