AKB 1820 Clarification

October 27, 2009

I just finished doing a “clean” uninstall (per akb 1820) of NS 7 to fix an issue in AKB 26197. After attempting a reinstall via SIM7 I was getting an error when trying to install the Symantec Management Platform by itself or as part of the client management suite. Altiris knowledge base article 1820 covers the process one must complete to do a manual uninstall of Notification Server. In short the article states:

  1. Backup your existing Altiris or AeXNS (this is optional, but recommended).
  2. Backup custom files: This includes Patches, Software Delivery packages, and any other customized files within your Notification Server installation. This does not include core program files.
  3. Stop any Altiris Service using the Services Manager
  4. Uninstall All Solutions, Notification Server, and the Altiris Agent from Add or Remove Programs.  Do *not* remove the Wise Toolkit if it is installed. This may cause IIS from running correctly.
  5. Go into Regedit and delete the following keys if they still exist:
    • HKLM > Software > Altiris and remove the keys: Altiris Agent, Communications, Scheduler, StartSoftwarePortal, StartCMS, Software Management, Patch Management, APackageStub.
    • HKLM > Software > Altiris > Express and remove all keys except Boot Disk Creator, console, Winpk.log (these will exist if Deployment Server is installed).
    • Delete the HKCR\Installer\Products\4E5A8049C67… key and any other keys that relate to Altiris including AppWeaver, Alert Manager, etc. (This will require you to explore the keys to find Altiris references, whether by Solution name or Altiris).
    • DeleteHKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Userdata\S-1-5-18\Products\ any of the IDs that correspond to Altiris.
    • Delete HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\ any of the IDs that correspond to Altiris.
    • Delete HKLM\SYSTEM\CurrentControlSet\Services any of the Altiris services.
  6. Delete the follow locations on the drive where Notification Server was installed:
    • Install path\Program Files\Altiris\Notification Server
    • From Windows: delete any Aex files in Winnt\System32
    • From Windows: delete any MSI files in WINNT\Installer related to Altiris (Look at the MSI properties).
    • Install path\Program Files\Altiris\Setup Files
  7. Reinstall Notification Server. (Use the version from www.solutionsam.com/solutions/6_0/ to make sure you have the most current version.)

Number 6 is in need of a little clarification. Where it says to delete any items related to altiris from HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Userdata\S-1-5-18\Products\. The only way to know if these keys relate to altiris is to expand the key and click on the installerproperties subkey and then reference the values in the right pane to see if they say anything about Altiris, if they do then delete the entire key related to that installer.

Note: This is for Altiris NS 6 but I applied it NS 7 without incident, ymmv.

Update!: This did not fix the SIM7 installer issue I experienced. There was an event log error reporting that NS 5.5 must be uninstalled before NS 6.0 can be installed. This was puzzling since we’re trying to install NS 7. The fix is to delete the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\UpgradeCodes\BD07D9FBBCB1C4A4394A9F46F2FACC2D This should take care of the problem, I was able to relaunch SIM7 and install the SMP without issue.

Advertisements

DS 6.9 SP3 & PXE

October 14, 2009

Just a friendly reminder here: When you upgrade to DS 6.9 SP3, make sure you either choose to update your PXE server through the SP3 install wizard or go back and relaunch C:\DSSetup\setup.exe (C: can be different in your environment) and choose component installation and choose to install a PXE server to upgrade to the latest build.

Failing to update the PXE server after the DS is running SP3 will result in clients booting into automation only to be struck by a \BOOT\BCD error before downloading the WinPE ISO.

Thank you VBS Gods.

October 8, 2009

We are working on a Cisco VoIP deployment and I’m currently using our 3 Altiris Deployment 6.9SP3 servers to push out the Cisco Desktop and Supervisor agents. We ran into a small snag to say the least. The cisco agents have an OS check in the MSI’s that prevent them from installing on Windows 7. Our core IT group is running Win 7 right now including the HD supervisor.

After a quick google on a super easy way to remove an OS check from an MSI I found this. Be aware that you need to go through the text you paste into notepad and replace the single and double quotes with the standard single/double quotes in notepad and save it with the .vbs extension.

After dropping the MSI’s onto the VBS they install and run in Windows 7 just fine which is not surprising considering they are vista compatible. Cheers to not waiting a week or more on an answer from cisco.

Disk2VHD 1.0 Announced

October 8, 2009

Sysinternals has just released a new tool called Disk2VHD. This tool will create a snapshot of any physical machine and turn it into a VHD allowing you to add it to Hyper-V or Windows Virtual PC.

You can find the tool here. Hope you enjoy, thanks sysinternals!

More Content Soon!

February 17, 2009

I will be publishing more content very soon out to The Juice. I will be sure and link to it from here. Thank you to everyone who has contacted me regarding #3 for the Hardware Independent Imaging article, it is on the way soon!

Busy Busy Busy!

October 16, 2008

Have been so busy lately with work and things we are doing there. Binding macs to the domain, gathering advanced inventory of them through Inventory tasks from the notification server. I have the 3rd piece of the imaging series as well as another article for updating the ProcessorDesc.ini file to add descriptions for newer processors.

Should have these articles to the juice in the next week… so sorry for the long delay on the imaging article.

In other news, I have passed my Notification System Foundation exam with a 96% 🙂

This Altiris Juice article that I’ve written details the differences between using “model_num” and “prod_name” when doing hardware independent imaging. You can view the post here. Be sure to read dfrancis’s comment at the end of the story, very interesting.

I have started a 3 part series on the Altiris Juice website that cover building a master image. You can find part 1 here. You can find part 2 here. Part 3 is finished but has not been uploaded or published on the site. More to follow!

My article covering the installation of the NS and DS agents for Macintosh has been posted on The Juice. Here is an excerpt

“Macintosh information for Altiris is a little sparse and I’ve often been left in the cold with questions. Hopefully this article will help guide those who are trying to get Macs to show up in the Deployment Console.”

You can read the rest of the article here.

I wrote an article for the Altiris Juice website which was published. You can take a look at the article here.