Highlights of this release include:
- Receiving Enhancements
- Supports workflows between PR auto-fill selector
- New summary screens
- New Reports & Notification Policies
- Cost Management
- Multi-currency
- Depreciation allocations
- Additional reporting for rollup cost/depreciation
12 January 2007
AexMachINV.exe process does not stop on servers
AexMachINV.exe process does not stop on servers; rows and rows of calls to gethostbyaddr() using what appears to be a garbage address
A fix is available in KB : http://kb.altiris.com/article.asp?article=22442&p=3
The official fix will be shipped with the SP2 version of IS 6.1. |
02 January 2007
How to determine when the Altiris agent last requested an update from the Notification server
Question
How to determine when the last time a specific PC requested (or checked for) a policy update from the NS, without checking the agent on the client PC itself.
Answer
You can check a single asset by just right clicking on it in NS and selecting Resource Manager. In the Summaries tab you can then drill down to Resource Manager, Resource Summary, and then in the right pane under "Altiris Agent Details" you will see when the agent was First discovered, Last Configuration Requested, Last Inventory Received and Last Event Received times.
For a fleet wide inventory report, go to the "Reports" tab in NS and under Notification Server Infrastructure, Agent, Altiris Agent Inventory you will see a number of reports, notably "Altiris Agent basic inventory (no update N days)" and "Altiris Agent basic inventory (sorted by last update)".
For a fleet wide "Configuration Request" report, a few items below you will see Configuration Request node. In there you will see a number of other reports, notably "Clients with no configuration in last N days".
Another report that may be useful is the "Configuration request statistics by time" which may be useful in analysing the peak times and traffic due to your current policy configurations
Link : KB Article
How to determine when the last time a specific PC requested (or checked for) a policy update from the NS, without checking the agent on the client PC itself.
Answer
You can check a single asset by just right clicking on it in NS and selecting Resource Manager. In the Summaries tab you can then drill down to Resource Manager, Resource Summary, and then in the right pane under "Altiris Agent Details" you will see when the agent was First discovered, Last Configuration Requested, Last Inventory Received and Last Event Received times.
For a fleet wide inventory report, go to the "Reports" tab in NS and under Notification Server Infrastructure, Agent, Altiris Agent Inventory you will see a number of reports, notably "Altiris Agent basic inventory (no update N days)" and "Altiris Agent basic inventory (sorted by last update)".
For a fleet wide "Configuration Request" report, a few items below you will see Configuration Request node. In there you will see a number of other reports, notably "Clients with no configuration in last N days".
Another report that may be useful is the "Configuration request statistics by time" which may be useful in analysing the peak times and traffic due to your current policy configurations
Link : KB Article
18 December 2006
Tool to make Unattend Install better
Have you ever wanted to remove Windows components like Media Player, Internet Explorer, Outlook Express, MSN Explorer, Messenger...
How about not even to install them with Windows ?
nLite is a tool for permanent Windows components removal and pre-installation Windows setup. After removal there is an option to make bootable image ready for burning on cd or testing in virtual machines. With nLite you will be able to have Windows installation which on install doesn't include, or even contain on cd, unwanted components.
Check this out...Link
How about not even to install them with Windows ?
nLite is a tool for permanent Windows components removal and pre-installation Windows setup. After removal there is an option to make bootable image ready for burning on cd or testing in virtual machines. With nLite you will be able to have Windows installation which on install doesn't include, or even contain on cd, unwanted components.
Check this out...Link
14 December 2006
Import/Export Utility
A new utility has been created to aid the import and export of items to the Notification Server.
Previously, users were able to export XML of unlimited size but there was a limit on import which
led to discrepancies. This utility was introduced to overcome import problems which occurred
when large amounts of data were being imported to the Notification Server.
The ImportExportUtil will be stored in the Install path\Diagnostics when the
Notification Server is installed. It is a console application that lets you to import/export, to and
from, the Notification Server database.
To run the application, double-click the ImportExportUtil.exe and follow the instructions in the
Command Window.
Note: The .exe file needs to be located in the same folder as the AeXImportExport.exe.config
and the utility user must be a member of Altiris Administrators.
(This information can be found in the release notes op NS6.0 SP3 except the file location is wrong in the release notes)
Previously, users were able to export XML of unlimited size but there was a limit on import which
led to discrepancies. This utility was introduced to overcome import problems which occurred
when large amounts of data were being imported to the Notification Server.
The ImportExportUtil will be stored in the Install path\Diagnostics when the
Notification Server is installed. It is a console application that lets you to import/export, to and
from, the Notification Server database.
To run the application, double-click the ImportExportUtil.exe and follow the instructions in the
Command Window.
Note: The .exe file needs to be located in the same folder as the AeXImportExport.exe.config
and the utility user must be a member of Altiris Administrators.
(This information can be found in the release notes op NS6.0 SP3 except the file location is wrong in the release notes)
Case Intrusion Detected on Dell Computers
There is a known issue when installing and using Dell Client Manager.
In some cases there will be a popup for chasis intrusion.
The following KB explains a solution for this problem
http://kb.altiris.com/article.asp?article=29004&p=3
In some cases there will be a popup for chasis intrusion.
The following KB explains a solution for this problem
http://kb.altiris.com/article.asp?article=29004&p=3
13 December 2006
Altiris Console 6.5 Hotfix (KB25949)
Where to Download Altiris Console 6.5 Hotfix (KB25949)
1. The Console 6.5 hotfix is attached to this article. Download the hotfix Altiris_Console_6_5_KB25949.exe. 2. Run Altiris_Console_6_5_KB25949.exe on the Notification Server.
Fixes:
· Altiris Console 6.5 with Recovery Solution 6.2 integration: Computer Collections and Cluster Settings context menu does not show all options of Recovery Solution Tasks
· Assets are not pointing to the correct pages
· Security Roles view doesn't appear properly
· After Editing a Web Part Report Link with an Extremely Long URL, the Apply Button disappears.
· Web.config debug is set to TRUE· Web Part edit page always disables the report picker
Reference :
http://kb.altiris.com/article.asp?article=25949&p=3
1. The Console 6.5 hotfix is attached to this article. Download the hotfix Altiris_Console_6_5_KB25949.exe. 2. Run Altiris_Console_6_5_KB25949.exe on the Notification Server.
Fixes:
· Altiris Console 6.5 with Recovery Solution 6.2 integration: Computer Collections and Cluster Settings context menu does not show all options of Recovery Solution Tasks
· Assets are not pointing to the correct pages
· Security Roles view doesn't appear properly
· After Editing a Web Part Report Link with an Extremely Long URL, the Apply Button disappears.
· Web.config debug is set to TRUE· Web Part edit page always disables the report picker
Reference :
http://kb.altiris.com/article.asp?article=25949&p=3
12 December 2006
Finally: Some info about the Database structure for NS
Altiris has released some SQL scripts to get more info about the database schema.
You don't get a manual or so, but some SQL Scripts to show and capture the DB structure
You don't get a manual or so, but some SQL Scripts to show and capture the DB structure
11 December 2006
Remote performance slow due to java script loading
Problem/Symptoms
When loading most console pages and dialogs client side scripting occurs using java script files. Whenever these files are loading from the server they will throw a 401 (access denied) error before requesting authentication from the browser. This causes a large delay in the loading of these pages.
Cause
IE does not expect authentication on JS files so always tries to run them anonymously, only trying authentication when rejected.
Resolution
Download SP3 KB25133 Update (R3) from: http://www.solutionsam.com/solutions/6_0/Altiris_NS_6_0_SP3_KB25133.exe
When loading most console pages and dialogs client side scripting occurs using java script files. Whenever these files are loading from the server they will throw a 401 (access denied) error before requesting authentication from the browser. This causes a large delay in the loading of these pages.
Cause
IE does not expect authentication on JS files so always tries to run them anonymously, only trying authentication when rejected.
Resolution
Download SP3 KB25133 Update (R3) from: http://www.solutionsam.com/solutions/6_0/Altiris_NS_6_0_SP3_KB25133.exe
How to access the Carbon Copy Web console from a URL
To access the Basic Carbon copy Web console page: http://ns-machine-name/Altiris/CarbonCopy/CarbonCopy.aspx?Name=&Timeout=60
To Access the Advanced Carbon Copy Web console page: http://ns-machine-name/Altiris/CarbonCopy/CarbonCopyFull.aspx?Name=&Timeout=60
To create a link to connect to a Carbon Copy Agent automatically (Basic): http://ns-machine-name/Altiris/CarbonCopy/CarbonCopy.aspx?IpAdd=cc-agent-name
To create a link to connect to a Carbon Copy Agent automatically(Advanced): http://ns-machine-name/Altiris/CarbonCopy/CarbonCopyFull.aspx?IpAdd=cc-agent-name
Note: Make sure to substitute the name of the notification server where the Carbon Copy solution is installed for "ns-machine-name" and the machine name where the Carbon Copy agent is installed for "cc-agent-name" within the links above
To Access the Advanced Carbon Copy Web console page: http://ns-machine-name/Altiris/CarbonCopy/CarbonCopyFull.aspx?Name=&Timeout=60
To create a link to connect to a Carbon Copy Agent automatically (Basic): http://ns-machine-name/Altiris/CarbonCopy/CarbonCopy.aspx?IpAdd=cc-agent-name
To create a link to connect to a Carbon Copy Agent automatically(Advanced): http://ns-machine-name/Altiris/CarbonCopy/CarbonCopyFull.aspx?IpAdd=cc-agent-name
Note: Make sure to substitute the name of the notification server where the Carbon Copy solution is installed for "ns-machine-name" and the machine name where the Carbon Copy agent is installed for "cc-agent-name" within the links above
08 December 2006
Patch Management Upgrade best practice from 6.1 to 6.2
Please read the following document when upgrading to PM6.2
http://kb.altiris.com/article.asp?article=30816&p=3
05 December 2006
Language Setting of the browser
In the internet browser you can change the language setting.
Deleting that one give a couple of strange errors like the missing 2 left pane in DSWEB and Itempicker control...
So be sure to have at least one language selected in your browser
Deleting that one give a couple of strange errors like the missing 2 left pane in DSWEB and Itempicker control...
So be sure to have at least one language selected in your browser
01 December 2006
Patch Management 6.2
Still a lot of issues with PM6.2.
I'm even under the impression they released it a bit early...
This KB is a summary of all important known issues http://kb.altiris.com/article.asp?article=29104&p=3
WINPE 2.0 (Vista) + Download link
Client Management Security Suite
Its finally released....the Clients Security Suite, containing:
Local Security
EndPoint Security
Audit and Compliance
Application Control
All in one suite, so one price...;-)
Local Security
EndPoint Security
Audit and Compliance
Application Control
All in one suite, so one price...;-)
29 November 2006
Release Notes of R3 for NS6.0SP3
Here you can find the release notes on the latest rollup for SP3 of NS6.0
It combines fixes for the issues addressed here
KB24764 KB24537 KB25767 KB27776 KB26457 KB26458
KB26459 KB26460 KB26463 KB26464 KB27777 KB26466
KB27778 KB27779 KB28017
Release Notes: http://kb.altiris.com/article.asp?article=25133&p=3
How can I find active computers which aren't sending Patch Management Inventory Summary data?
Create a new report, and choose to enter the SQL manually. Copy and paste the following:
________________________________
________________________________
SELECT vC.[Name], vC.[Domain], vC.[OS Name], vC.[OS Type], a.LastConfig, vC.[Guid]
FROM vComputerEx vC
INNER JOIN Inv_AeX_AC_Client_Agent acca
ON vC.[Guid] = acca.[_ResourceGuid]
INNER JOIN (
SELECT ResourceGuid, LastConfig = datediff(dd,MAX([StartTime]),GETDATE()),
LastConfigDate = MAX([StartTime])
FROM Evt_NS_Client_Config_Request
GROUP BY ResourceGuid
HAVING DATEDIFF(dd,MAX([StartTime]),GETDATE()) <= 30 --change to a lower number if desired
) AS a
ON a.ResourceGuid = vc.Guid
WHERE 1 = 1
AND vC.[Guid] NOT IN (
SELECT DISTINCT _ResourceGuid
FROM Evt_Inventory_Rule_Summary
)
AND acca.[Agent Name] = 'Altiris Software Update Agent'
________________________________
The results of this report will be all machines which have requested configuration from the NS within the last 30 days but have not sent an Inventory Rule summary (or the Inventory was rejected by the NS for some reason due to some problem).
26 November 2006
Don't like the PXE menu from DS6.8?
Found a noce article on the juice site....
http://juice.altiris.com/node/759/
And here an example : http://juice.altiris.com/download/837/pxe-menu-happy-thanksgiving
http://juice.altiris.com/node/759/
And here an example : http://juice.altiris.com/download/837/pxe-menu-happy-thanksgiving
25 November 2006
Get log information of server or managed PC
When run on a managed PC this will show the logview page for this PC
http://"servername"/Altiris/NS/logview.asp?server="PCNAME"
When this is run then the log of the NS server is shown
http://"servername"/Altiris/NS/logview.asp
http://"servername"/Altiris/NS/logview.asp?server="PCNAME"
When this is run then the log of the NS server is shown
http://"servername"/Altiris/NS/logview.asp
Patch Management 6.2 released
Patch Management 6.2 has being released (Support for Dutch Langues Patches).
See http://kb.altiris.com/article.asp?article=29579&p=3 for the Release Notes
But still a lot of know issues...
See http://kb.altiris.com/article.asp?article=29579&p=3 for the Release Notes
But still a lot of know issues...
21 November 2006
Support for Windows 2003 SP1
A list is available in the kb of what version of components are supported in Win 2003 SP1
SWD Plug in Task Server
The SWD Plug in for Task server is released...
But .... You wont see it as an update so you need either to install it directly from the solutionsam, or go to Available Solution, Solutions and then Software Delivery Solution, there you see the Plug In will be installed.
But .... You wont see it as an update so you need either to install it directly from the solutionsam, or go to Available Solution, Solutions and then Software Delivery Solution, there you see the Plug In will be installed.
Support for SQL 2005 SP1
Service Pack 1 for SQL 2005 was released on April 18, 2006. The Altiris testing methodology is to ensure that all new versions of Altiris solutions are compatible with current technology. Therefore, any solution that was released or upgraded on or after June 2006 is supported for SQL 2005 SP1
A list of the version that are supported can be found in this KB
A list of the version that are supported can be found in this KB
15 November 2006
03 November 2006
Application Control Released
Release notes can be found here
With Application Control Solution you can:
Implement the principle of least privilege in order to enhance protection of data and functionality from faults and malicious behavior. See Restrict an Application’s
Process Rights
Apply security ratings to withstand future attacks by reducing attack surface. You
can reduce the attack surface by reducing the number of applications available to
exploitation. See Security Rating.
Isolate an application to protect against file system and registry corruption or
misuse. This is done through integration with Altiris® Software Virtualization
Solution™ software. See Run an Application in an SVS Layer
Protect against data theft. You can automate the encryption of documents as
Application Control Solution seamlessly integrates with Windows Encrypted File
System. For information, see http://www.microsoft.com/resources/documentation/
windows/xp/all/proddocs/en-us/encrypt_overview.mspx?mfr=true. Using
Application Control Solution, you can automatically encrypt documents on a
notebook, thus preventing theft. See Automate Document Encryption.
Control an application’s ability to read or write to specific network locations.
Prevent potentially malicious applications, such as keyloggers, from installing
Windows API hooks. See Manage Applications.
Protect from viruses and spyware. See Quarantine Files.
With Application Control Solution you can:
Implement the principle of least privilege in order to enhance protection of data and functionality from faults and malicious behavior. See Restrict an Application’s
Process Rights
Apply security ratings to withstand future attacks by reducing attack surface. You
can reduce the attack surface by reducing the number of applications available to
exploitation. See Security Rating.
Isolate an application to protect against file system and registry corruption or
misuse. This is done through integration with Altiris® Software Virtualization
Solution™ software. See Run an Application in an SVS Layer
Protect against data theft. You can automate the encryption of documents as
Application Control Solution seamlessly integrates with Windows Encrypted File
System. For information, see http://www.microsoft.com/resources/documentation/
windows/xp/all/proddocs/en-us/encrypt_overview.mspx?mfr=true. Using
Application Control Solution, you can automatically encrypt documents on a
notebook, thus preventing theft. See Automate Document Encryption.
Control an application’s ability to read or write to specific network locations.
Prevent potentially malicious applications, such as keyloggers, from installing
Windows API hooks. See Manage Applications.
Protect from viruses and spyware. See Quarantine Files.
02 November 2006
01 November 2006
What to know about SWD 6.1SP2
Things to Know for 6.1 SP2
In Software Delivery Solution Task Server Plug-in, the Post Program Run Actions are handled through the Task Server
In Software Delivery Solution Task Server Plug-in, the post program run actions, such as No action required, Restart computer, and Log off user are handled by the Task Server. The After Running drop-down list on the Programs tabview of the Packages page lists all the post program run actions.
On the Task Server a Task Server Power Management task needs to be added to a job. The Task Server Power Management task takes care of post program run actions that are required to be carried out.
Installation, Upgrade, and Uninstallation
Prerequisites
On the Target Computer
Altiris Agent
Client Task Agent 2.3
On the Notification Server
Notification Server 6.0 SP3 or later
For Software Delivery Task Server Plug-in
Altiris Task Management 6.0
Software Delivery Solution 6.1 SP 1 or later
Custom Console 6.5 and Custom Console Data 6.5
In Software Delivery Solution Task Server Plug-in, the Post Program Run Actions are handled through the Task Server
In Software Delivery Solution Task Server Plug-in, the post program run actions, such as No action required, Restart computer, and Log off user are handled by the Task Server. The After Running drop-down list on the Programs tabview of the Packages page lists all the post program run actions.
On the Task Server a Task Server Power Management task needs to be added to a job. The Task Server Power Management task takes care of post program run actions that are required to be carried out.
Installation, Upgrade, and Uninstallation
Prerequisites
On the Target Computer
Altiris Agent
Client Task Agent 2.3
On the Notification Server
Notification Server 6.0 SP3 or later
For Software Delivery Task Server Plug-in
Altiris Task Management 6.0
Software Delivery Solution 6.1 SP 1 or later
Custom Console 6.5 and Custom Console Data 6.5
31 October 2006
Application Metering and Software Delivery Updated
Most bug fixes....for App Metering
SWD 6.1SP2 :
Release Notes
What's New in this Release
What is New in this Release?
Updated User Interface for Data Purging
Software Delivery Solution Task Server Plug-in
Known Issues
The following are unresolved issues and workaround instructions for issues in this release:
Known Issue Article ID
Software Portal functions incorrectly due to the unregistered MSCOMCTL.OCX file 26018
A duplicate copy of software delivery package is created on the client computer 26021
Clicking a New Program tool opens a Software Delivery Program Page 26245
Deliver Software task fails the first time for the packages that have Package Servers option set to manual pre-staging 26244
SWD 6.1SP2 :
Release Notes
What's New in this Release
What is New in this Release?
Updated User Interface for Data Purging
Software Delivery Solution Task Server Plug-in
Known Issues
The following are unresolved issues and workaround instructions for issues in this release:
Known Issue Article ID
Software Portal functions incorrectly due to the unregistered MSCOMCTL.OCX file 26018
A duplicate copy of software delivery package is created on the client computer 26021
Clicking a New Program tool opens a Software Delivery Program Page 26245
Deliver Software task fails the first time for the packages that have Package Servers option set to manual pre-staging 26244
06 October 2006
07 September 2006
Why do I receive a "Server Error in '/Altiris/NS' Application after instaling KB23784 (R2)?
After installing KB23784 (R2) onto five NS SP3 computers, I found that I could no longer access the Altiris Console on two of them
21 August 2006
How to determine which Dell systems may have a battery for recall.
How to determine which Dell systems may have a battery for recall.
Question | |
How do you determine which systems in your environment may have a battery that needs to be replaced with the Dell laptop battery recall? | |
Answer | |
You can run the following SQL query. NOTE: This query requires that your Notification Server have the Dell Client Manager installed. Select vc.[name] AS 'Computer Name', | |
03 August 2006
Solution Removal Tool (Removes Solution from Database)
| Problem | |
| Sometimes after uninstalling a solution from either the Add/Remove Programs or from the Solution Center you find that this has not removed the solution completely from the Database. Some symptoms that you will see is referrences to the Solution in the Tree Structure on the Notification Server Admin Console. You may also see a refference to the Solution when attempting to view the GetLicenseDetails.aspx page which would returns a ASP Dump. | |
| Environment | |
| Cause | |
| At this time the root cause is undetermined. It may be a combination of things including SQL Deadlocks or Security. | |
| Resolution | |
Use the following Solution Removal Tool. In the sample below this will remove Web Administrator for Windows from the Altiris Database. Please remeber when running this tool to select the correct database to run the query against. Please note that you use this Removal Tool at your own risk, Database backup is higly recommended before running. REM Replace GUID with Product GUID of the Solution you wish to Remove from the Altiris Database SET @GUID = '{B2CF75A5-C442-4945-A979-1EAFDD182A76}' Delete from Item where Guid = @Guid | |
02 August 2006
Script to install SVS Agent
Question
How do you do a silent install of the Software Virtualization Agent?
Answer
Run the following from a command line or in a script:
msiexec.exe /qb? /i\Software_Virtualization_Agent.msi PRODUCT_KEY=
Replace:
= Path to folder containing Software_Virtualization_Agent.msi
= Your SVS product key in xxxx-xxxx-xxxx-xxxx format
How do you do a silent install of the Software Virtualization Agent?
Answer
Run the following from a command line or in a script:
msiexec.exe /qb? /i
Replace:
01 August 2006
28 June 2006
DS Console slow to load, freezes, or users in AD groups don't have correct rights in the console after console opens
A) OU Structure is usually the biggest cause of this. When a user object exists in a Sub OU that is too deep or the Sub OU has commas in it, the DS Console will display the following symptoms:
Slow load for the console.
Cannot log onto the console.
Console freezes when security is enabled.
When logged on, the user has no rights even though AD group has the correct rights set.
B) DNS Queries can have issues when running in an isolated environment. This is usually displayed by a DS Console taking 2-5 minutes to log into.
--------------------------------------------------------------------------------
Resolution
There is a new express.exe that fixes most of these issues. Attached is that .EXE in ZIP format. This express.exe will need to be licensed with a valid eXpress license. DS 6.5 SP1 needs to be installed prior to this fix.
You can download the .EXE from the KB When clicking on this link
Slow load for the console.
Cannot log onto the console.
Console freezes when security is enabled.
When logged on, the user has no rights even though AD group has the correct rights set.
B) DNS Queries can have issues when running in an isolated environment. This is usually displayed by a DS Console taking 2-5 minutes to log into.
--------------------------------------------------------------------------------
Resolution
There is a new express.exe that fixes most of these issues. Attached is that .EXE in ZIP format. This express.exe will need to be licensed with a valid eXpress license. DS 6.5 SP1 needs to be installed prior to this fix.
You can download the .EXE from the KB When clicking on this link
31 May 2006
How to compress WinPE PXE Images
You can create a compressed WinPE PXE Image in an SDI file. This will reduce the image size by 35 percent. A PXE Image that is normally 145 MB will be reduced to 95 MB
You find more info in this KB of Altiris
You find more info in this KB of Altiris
08 May 2006
Link to : Using Software Delivery Solution to Install Internet Explorer ActiveX Compatibility Patch for Mshtml.dll
http://kb.altiris.com/article.asp?article=21749&p=3
This article contains a download link to the XML ( at the right side of the page )
This article contains a download link to the XML ( at the right side of the page )
25 April 2006
Installing/Updating Aclient + custom settings with Altiris job
From the deployment console, use the remote agent installer tool, change the agent settings the way you want them, by clicking the change settings button, Add a test computer but dont click the finish button, click on export, this will export clients.rci file which holds the settings, then rename that clients_pcname.inp file
to Aclient.inp. You can do two things with the Aclient.inp.
Create a deployment job to install the Aclient using these settings by running something like
Aclient.exe aclient.inp -Install -Silent
Or if you just want to change settings and not install aclient,, create a copy job in DS
Point the file to copy to the aclient.inp
use the destination just like
settings:aclient.inp
Thx Tim.
Steve Gibson made a GPO for this, you can find more info at : Steve's site
Thx Steve
to Aclient.inp. You can do two things with the Aclient.inp.
Create a deployment job to install the Aclient using these settings by running something like
Aclient.exe aclient.inp -Install -Silent
Or if you just want to change settings and not install aclient,, create a copy job in DS
Point the file to copy to the aclient.inp
use the destination just like
settings:aclient.inp
Thx Tim.
Steve Gibson made a GPO for this, you can find more info at : Steve's site
Thx Steve
Helpdesk: These common words were ignored:" every word we search for"
Here is what I suggest you try, keeping in mind all the best practices concerning backups and testing and not suing me if something goes wnrgo:
Using SQL Enterprise Manager, expand the incident database (usually Altiris_Incidents), then click on Full-Text catalogs. There should be one: HD_workitem_comment. Right-click on that and choose " Rebuild catalog" .
Also, find the workitem table in Tables and right-click on that. Drill into the Full-Text Index menu and make sure Change Tracking and Update Index in Background are checked. That' s what keeps the full-text index up to date.
SQL 2005 has a new UI that is a little different but the same basic capabilities are there: look under the Storage folder to find the full-text catalog. The Full-Text Index menu for the workitem table has Track Changes Automatically available as a choice if tracking hasn' t been turned on.
It seems like SP3 doesn' t correctly turn that tracking on for SQL 2005 when you create a new database. I don' t know why it would turn it off on sql 2003 or 2000 if it was on previously. Are these new databases that you' re seeing the problem in?
Using SQL Enterprise Manager, expand the incident database (usually Altiris_Incidents), then click on Full-Text catalogs. There should be one: HD_workitem_comment. Right-click on that and choose " Rebuild catalog" .
Also, find the workitem table in Tables and right-click on that. Drill into the Full-Text Index menu and make sure Change Tracking and Update Index in Background are checked. That' s what keeps the full-text index up to date.
SQL 2005 has a new UI that is a little different but the same basic capabilities are there: look under the Storage folder to find the full-text catalog. The Full-Text Index menu for the workitem table has Track Changes Automatically available as a choice if tracking hasn' t been turned on.
It seems like SP3 doesn' t correctly turn that tracking on for SQL 2005 when you create a new database. I don' t know why it would turn it off on sql 2003 or 2000 if it was on previously. Are these new databases that you' re seeing the problem in?
19 April 2006
Deployment Solution 6.5 Hardware Independent Imaging
here you can find how to make an hardware independent image for to be used with Deployment Server 6.5 and Sysprep
http://kb.altiris.com/article.asp?article=21224&p=3
http://kb.altiris.com/article.asp?article=21224&p=3
18 April 2006
Using Software Delivery Solution to Install Internet Explorer ActiveX Compatibility Patch for Mshtml.dll (MS06-013)
Using Software Delivery Solution to Install Internet Explorer ActiveX Compatibility Patch for Mshtml.dll
Problem
The Altiris Console reacts differently to ActiveX Controls after installing the patches included in Microsoft's KB article 912945, "Internet Explorer ActiveX update," or KB912812, "MS06-013: Cumulative security update for Internet Explorer."
Environment
Microsoft Windows XP Service Pack 2
Microsoft Windows Server 2003 Service Pack 1 (SP1)
Notification Server 6.0 SP3 (6.0.6074), older versions will most likely react to the ActiveX update in the same way.
Cause
Microsoft made minor changes to the way that Internet Explorer handles some Web pages that use ActiveX controls. See Microsoft Security Advisory (912945) published Feb 28,1006:
http://www.microsoft.com/technet/security/advisory/912945.mspx
and press release:
http://www.microsoft.com/presspass/press/2003/oct03/10-06EOLASpr.mspx
Resolution
Install Microsoft Compatibility Patch KB917425 Internet Explorer ActiveX compatibility patch for Msdhtml.dll. See:
http://support.microsoft.com/kb/917425/en-us
Note: You only need to install this patch if you have previously installed the KB912945 or KB912812 patches. This patch should give you an error if you have not previously installed one of the other two patches. The preferred method of installing these patches is to follow the instructions on the Microsoft Web site, especially for your Microsoft 2003 Server computers.
However, to help facilitate the installation of these patches, you may download the attached Compatibility Patch (KB917425).xml file that contains two Software Delivery Tasks that utilize the same Software Delivery Package and import it into your Notification Server console.
Download both the Windows 2003 and Windows XP patch files from the URL above. The two filenames are:
WindowsServer2003-KB917425-x86-ENU.exe
WindowsXP-KB917425-x86-ENU.exe
Place these two files in a folder that is local to your NS server.
Import the Compatibility Patch (KB917425).xml file by right-clicking on a suitable location in your Console and selecting import. A good location might be the Task tab > Software Management > Software Delivery > Windows > Software Delivery Tasks.
Modify the Package Location: field in the "ActiveX Compatibility Patch (KB917425)" package to point to the folder you created in step 1.
Apply the change and be sure to "Update Distribution Points".
The tasks are set to apply to the "All 32-bit Windows 2003 Servers"/"All 32-bit Windows XP Computers" collections. If the KB912945 or KB912812 patches are not installed on the computers in these collections, you will need to modify the Applies to collections: field appropriately.
Enable the tasks.
Problem
The Altiris Console reacts differently to ActiveX Controls after installing the patches included in Microsoft's KB article 912945, "Internet Explorer ActiveX update," or KB912812, "MS06-013: Cumulative security update for Internet Explorer."
Environment
Microsoft Windows XP Service Pack 2
Microsoft Windows Server 2003 Service Pack 1 (SP1)
Notification Server 6.0 SP3 (6.0.6074), older versions will most likely react to the ActiveX update in the same way.
Cause
Microsoft made minor changes to the way that Internet Explorer handles some Web pages that use ActiveX controls. See Microsoft Security Advisory (912945) published Feb 28,1006:
http://www.microsoft.com/technet/security/advisory/912945.mspx
and press release:
http://www.microsoft.com/presspass/press/2003/oct03/10-06EOLASpr.mspx
Resolution
Install Microsoft Compatibility Patch KB917425 Internet Explorer ActiveX compatibility patch for Msdhtml.dll. See:
http://support.microsoft.com/kb/917425/en-us
Note: You only need to install this patch if you have previously installed the KB912945 or KB912812 patches. This patch should give you an error if you have not previously installed one of the other two patches. The preferred method of installing these patches is to follow the instructions on the Microsoft Web site, especially for your Microsoft 2003 Server computers.
However, to help facilitate the installation of these patches, you may download the attached Compatibility Patch (KB917425).xml file that contains two Software Delivery Tasks that utilize the same Software Delivery Package and import it into your Notification Server console.
Download both the Windows 2003 and Windows XP patch files from the URL above. The two filenames are:
WindowsServer2003-KB917425-x86-ENU.exe
WindowsXP-KB917425-x86-ENU.exe
Place these two files in a folder that is local to your NS server.
Import the Compatibility Patch (KB917425).xml file by right-clicking on a suitable location in your Console and selecting import. A good location might be the Task tab > Software Management > Software Delivery > Windows > Software Delivery Tasks.
Modify the Package Location: field in the "ActiveX Compatibility Patch (KB917425)" package to point to the folder you created in step 1.
Apply the change and be sure to "Update Distribution Points".
The tasks are set to apply to the "All 32-bit Windows 2003 Servers"/"All 32-bit Windows XP Computers" collections. If the KB912945 or KB912812 patches are not installed on the computers in these collections, you will need to modify the Applies to collections: field appropriately.
Enable the tasks.
Items to help improve Console and Server performance in Notification Server
QuestionWhat can be done to improve the speed of the Notification Server and Altiris Console? What items can increase efficiencies?
Answer
Disabling Alert Manager Synchronization
How to Disable Alert Manager and Notification Server synchronization: below are the registry changes needed to disable the synchronization functionality of AlertManager/Helpdesk. This has proved to produce performance improvements on busy notification servers where AlertManager/Helpdesk asset and contact synchronization from the Notification Server is not required.
Using regedit, add the following two REG_SZ entries :
HKLM\Software\Altiris\eXpress\Helpdesk Package\DisableAutoUpdateProcessing = true
HKLM\Software\Altiris\eXpress\Helpdesk Package\DisableSyncIncidentProcessing = true
Stop the Altiris Service (AeXSvc.exe) and the Altiris Client Message Dispatcher service.
Go to Start > Run, and type "iisreset" and click OK. This will recycle IIS, including the worker process.
Start the Altiris Service (AeXSvc.exe) and the Altiris Client Message Dispatcher service.
Increasing SQL Performance by defragging the SQL indices
Several defrags can increase SQL performance.
1. SQL script to defrag all database indices for the Altiris database:
declare @index_name nvarchar(255)
declare @table_name nvarchar(255)
declare index_cursor cursor for
select
si.name as index_name,
object_name(si.id) as table_name
from sysindexes si
left outer join sysobjects so on so.name=si.name
where objectproperty(si.id, N'IsUserTable') = 1
and objectproperty(si.id, N'IsUserTable') = 1
and si.name <> object_name(si.id)
and si.impid <> -1
open index_cursor
fetch next from index_cursor into @index_name, @table_name
while @@FETCH_STATUS = 0
begin
print 'Attempting defrag of index [' + @index_name + '] on table [' + @table_name + ']'
dbcc INDEXDEFRAG( 0, @table_name, @index_name )
fetch next from index_cursor into @index_name, @table_name
end
close index_cursor
deallocate index_cursor
2. The above script defrags all the indices used in the Altiris database. Run this against the Altiris database using SQL Query Analyser or other SQL scripting tool.
3. Defrag SQL data and log volumes. Post upgrade the log files of the Altiris database can be heavily fragmented. Use Enterprise Manager or similar SQL management tool to defrag these volumes to greatly improve SQL performance Post-upgrade.
SQL Configuration Optimization
The following items can increase SQL performance, thus increasing the speed of the Notification Server and the Altiris Console.
An I/O is generally a separate hard drive. This is not true when using ATA/IDE drives and the two drives are mastered and slaved. Consequently, the hard drives would need to be on separate IDE/ATA ribbon cables. For SCSI, two separate drives can be on the same SCSI cable.
In SQL enterprise manager open the database properties.
In the Data Files and Transaction Log tabs, note the current location of the .MDF and .NDF (if used) data file(s) and the .LDF transaction log file(s).
Close the properties and right-click on the database > All Tasks > Detach Database.
Once the database is detached, manually move the .MDF, .NDF (if used), and .LDF files.
One of the suggestions from Altiris development is to place the .LDF file(s) on a separate physical disk from the data file(s). This should allow transactions and data reads and writes to operate independently and concurrently.
After moving the .MDF, .NDF (if used), and .LDF files on the various drive locations, reattach to the database.
Open SQL enterprise manager, right-click on the Databases folder > All Tasks > Attach Database.
Use the ellipsis button ( … ) to browse to the current location of the .MDF file. This will populate a list of all the data files and their physical locations. The .MDF will be set based on the current location based on browsing with the ellipsis button. However, all the other data files will retain their paths as it knew them before the database was detached.
Each path location will need to be corrected for the new location of that file until the red X turns into a green checkmark.
Once all the file path locations have been set correctly, make sure that the database is the correct database name.
Click Verify and then, if that does not bring any errors, hit OK.
The database will not be using the new locations for each of the files. This should be verified by the properties of the database on the Data Files and Transaction Log tabs.
Another suggestion that comes from SQL is to move the tempdb to a FAST I/O physical disk drive. This makes a lot of sense given how heavy Altiris uses the tempdb (anytime a temporary table is created). If the server has three physical disks, the operating system should be on one, most of the database files on the other, and the third, with the fastest I/O, should have the transaction logs and tempdb data files.
Moving the tempdb data files is done a little differently than moving data files of other database because the tempdb cannot be detached. Microsoft provided a different way to do this for the tempdb database only.
In Query Analyzer run this command (substitute the correct drive and folders, placing these files on a fast I/O drive)
ALTER DATABASE tempdb modify file (name=tempdev, FILENAME= ‘e:\SQLDATA\tempdb.mdf’)
ALTER DATABASE tempdb modify file (name=templog, FILENAME= ‘e:\SQLDATA\tempdb.ldf’)
Stop and restart SQL Server service
Verify that the new tempdb.mdf and tempdb.ldf files have been created. Then go ahead and delete the older original copy.
If there are more than three physical disks available it is possible to split a little further. Spanning the tempdb data files across multiple physical disks increases performance further.
Microsoft Recommended SQL Optimizations
The following are optimizations recommended by Microsoft for increased performance of SQL in general.
Optimizing Transaction Log Performance. General recommendations for creating transaction log files include:
Create the transaction log on a physically separate disk or RAID (redundant array of independent disks) device. The transaction log file is written serially. Therefore, using a separate, dedicated disk allows the disk heads to stay in place for the next write operation.
Set the original size of the transaction log file to a reasonable size to prevent the file from automatically expanding as more transaction log space is needed. As the transaction log expands, a new virtual log file is created. Write operations to the transaction log wait while the transaction log is expanded. If the transaction log expands too frequently, performance can be affected.
Set the file growth increment percentage to a reasonable size to prevent the file from growing by too small a value. If the file growth is too small compared to the number of log records being written to the transaction log, then the transaction log may need to expand constantly, affecting performance.
Manually shrink the transaction log files rather than allowing Microsoft SQL Server 2000 to shrink the files automatically. Shrinking the transaction log can affect performance on a busy system due to the movement and locking of data pages.
Optimizing tempdb Performance - General recommendations for the physical placement and database options set for the tempdb database include:
Allow the tempdb database to automatically expand as needed. This ensures that queries that generate larger than expected intermediate result sets stored in the tempdb database are not terminated before execution is complete.
Set the original size of the tempdb database files to a reasonable size to avoid the files from automatically expanding as more space is needed. If the tempdb database expands too frequently, performance can be affected.
Set the file growth increment percentage to a reasonable size to avoid the tempdb database files from growing by too small a value. If the file growth is too small compared to the amount of data being written to the tempdb database, then tempdb may need to expand constantly, thereby affecting performance.
Place the tempdb database on a fast I/O subsystem to ensure good performance. Stripe the tempdb database across multiple disks for better performance. Use file groups to place the tempdb database on disks different from those used by user databases
Answer
Disabling Alert Manager Synchronization
How to Disable Alert Manager and Notification Server synchronization: below are the registry changes needed to disable the synchronization functionality of AlertManager/Helpdesk. This has proved to produce performance improvements on busy notification servers where AlertManager/Helpdesk asset and contact synchronization from the Notification Server is not required.
Using regedit, add the following two REG_SZ entries :
HKLM\Software\Altiris\eXpress\Helpdesk Package\DisableAutoUpdateProcessing = true
HKLM\Software\Altiris\eXpress\Helpdesk Package\DisableSyncIncidentProcessing = true
Stop the Altiris Service (AeXSvc.exe) and the Altiris Client Message Dispatcher service.
Go to Start > Run, and type "iisreset" and click OK. This will recycle IIS, including the worker process.
Start the Altiris Service (AeXSvc.exe) and the Altiris Client Message Dispatcher service.
Increasing SQL Performance by defragging the SQL indices
Several defrags can increase SQL performance.
1. SQL script to defrag all database indices for the Altiris database:
declare @index_name nvarchar(255)
declare @table_name nvarchar(255)
declare index_cursor cursor for
select
si.name as index_name,
object_name(si.id) as table_name
from sysindexes si
left outer join sysobjects so on so.name=si.name
where objectproperty(si.id, N'IsUserTable') = 1
and objectproperty(si.id, N'IsUserTable') = 1
and si.name <> object_name(si.id)
and si.impid <> -1
open index_cursor
fetch next from index_cursor into @index_name, @table_name
while @@FETCH_STATUS = 0
begin
print 'Attempting defrag of index [' + @index_name + '] on table [' + @table_name + ']'
dbcc INDEXDEFRAG( 0, @table_name, @index_name )
fetch next from index_cursor into @index_name, @table_name
end
close index_cursor
deallocate index_cursor
2. The above script defrags all the indices used in the Altiris database. Run this against the Altiris database using SQL Query Analyser or other SQL scripting tool.
3. Defrag SQL data and log volumes. Post upgrade the log files of the Altiris database can be heavily fragmented. Use Enterprise Manager or similar SQL management tool to defrag these volumes to greatly improve SQL performance Post-upgrade.
SQL Configuration Optimization
The following items can increase SQL performance, thus increasing the speed of the Notification Server and the Altiris Console.
An I/O is generally a separate hard drive. This is not true when using ATA/IDE drives and the two drives are mastered and slaved. Consequently, the hard drives would need to be on separate IDE/ATA ribbon cables. For SCSI, two separate drives can be on the same SCSI cable.
In SQL enterprise manager open the database properties.
In the Data Files and Transaction Log tabs, note the current location of the .MDF and .NDF (if used) data file(s) and the .LDF transaction log file(s).
Close the properties and right-click on the database > All Tasks > Detach Database.
Once the database is detached, manually move the .MDF, .NDF (if used), and .LDF files.
One of the suggestions from Altiris development is to place the .LDF file(s) on a separate physical disk from the data file(s). This should allow transactions and data reads and writes to operate independently and concurrently.
After moving the .MDF, .NDF (if used), and .LDF files on the various drive locations, reattach to the database.
Open SQL enterprise manager, right-click on the Databases folder > All Tasks > Attach Database.
Use the ellipsis button ( … ) to browse to the current location of the .MDF file. This will populate a list of all the data files and their physical locations. The .MDF will be set based on the current location based on browsing with the ellipsis button. However, all the other data files will retain their paths as it knew them before the database was detached.
Each path location will need to be corrected for the new location of that file until the red X turns into a green checkmark.
Once all the file path locations have been set correctly, make sure that the database is the correct database name.
Click Verify and then, if that does not bring any errors, hit OK.
The database will not be using the new locations for each of the files. This should be verified by the properties of the database on the Data Files and Transaction Log tabs.
Another suggestion that comes from SQL is to move the tempdb to a FAST I/O physical disk drive. This makes a lot of sense given how heavy Altiris uses the tempdb (anytime a temporary table is created). If the server has three physical disks, the operating system should be on one, most of the database files on the other, and the third, with the fastest I/O, should have the transaction logs and tempdb data files.
Moving the tempdb data files is done a little differently than moving data files of other database because the tempdb cannot be detached. Microsoft provided a different way to do this for the tempdb database only.
In Query Analyzer run this command (substitute the correct drive and folders, placing these files on a fast I/O drive)
ALTER DATABASE tempdb modify file (name=tempdev, FILENAME= ‘e:\SQLDATA\tempdb.mdf’)
ALTER DATABASE tempdb modify file (name=templog, FILENAME= ‘e:\SQLDATA\tempdb.ldf’)
Stop and restart SQL Server service
Verify that the new tempdb.mdf and tempdb.ldf files have been created. Then go ahead and delete the older original copy.
If there are more than three physical disks available it is possible to split a little further. Spanning the tempdb data files across multiple physical disks increases performance further.
Microsoft Recommended SQL Optimizations
The following are optimizations recommended by Microsoft for increased performance of SQL in general.
Optimizing Transaction Log Performance. General recommendations for creating transaction log files include:
Create the transaction log on a physically separate disk or RAID (redundant array of independent disks) device. The transaction log file is written serially. Therefore, using a separate, dedicated disk allows the disk heads to stay in place for the next write operation.
Set the original size of the transaction log file to a reasonable size to prevent the file from automatically expanding as more transaction log space is needed. As the transaction log expands, a new virtual log file is created. Write operations to the transaction log wait while the transaction log is expanded. If the transaction log expands too frequently, performance can be affected.
Set the file growth increment percentage to a reasonable size to prevent the file from growing by too small a value. If the file growth is too small compared to the number of log records being written to the transaction log, then the transaction log may need to expand constantly, affecting performance.
Manually shrink the transaction log files rather than allowing Microsoft SQL Server 2000 to shrink the files automatically. Shrinking the transaction log can affect performance on a busy system due to the movement and locking of data pages.
Optimizing tempdb Performance - General recommendations for the physical placement and database options set for the tempdb database include:
Allow the tempdb database to automatically expand as needed. This ensures that queries that generate larger than expected intermediate result sets stored in the tempdb database are not terminated before execution is complete.
Set the original size of the tempdb database files to a reasonable size to avoid the files from automatically expanding as more space is needed. If the tempdb database expands too frequently, performance can be affected.
Set the file growth increment percentage to a reasonable size to avoid the tempdb database files from growing by too small a value. If the file growth is too small compared to the amount of data being written to the tempdb database, then tempdb may need to expand constantly, thereby affecting performance.
Place the tempdb database on a fast I/O subsystem to ensure good performance. Stripe the tempdb database across multiple disks for better performance. Use file groups to place the tempdb database on disks different from those used by user databases
Microsoft .NET Frequently Asked Questions (FAQ)
Question
This article (taken from the "Microsoft .NET FAQs" help topic in Wise for Windows Installer and the Windows Installer Editor) answers questions about Microsoft .NET and defines important concepts you should understand before you use Wise for Windows Installer or the Windows Intsaller Editor to build .NET installations.
Answer
What does the common language runtime do?
The common language runtime manages the execution of code and provides services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support. See Common Language Runtime in the MSDN Library.
What's the difference between managed and unmanaged code?
Code developed with a language compiler that targets the common language runtime is called managed code. All code based on Microsoft intermediate language (MSIL) executes as managed code. Managed code is self-describing; it contains metadata that describes every element managed by the common language runtime. The runtime uses the metadata to provide services.
Code that runs outside the runtime and does not contain metadata is called unmanaged code. Examples of unmanaged code are COM components, ActiveX interfaces, and Win32 API functions. Unmanaged code executes in the common language runtime environment with minimal services.
I don't want to rewrite all my applications as managed code. Can I add managed code to an existing application?
Few developers will be able to rewrite existing applications completely as managed (.NET) code. Instead, you can combine managed and unmanaged components in one installation. Code that contains a mix of managed and unmanaged elements is called interoperable code.
The common language runtime supports COM interoperability (interop). For backward compatibility, COM interop provides access to existing COM components without requiring you to modify the original components. COM interop also enables your COM clients to access managed code as easily as they access other COM objects. This is accomplished by adding information to the system registry so .NET components are called as though they were COM components. At runtime, the common language runtime marshals data between COM objects and managed objects as needed.
See Interoperating with Unmanaged Code in the MSDN Library.
What is an assembly?
An assembly is the primary building block of a .NET application. An assembly contains its own naming, binding, versioning, deployment, and configuration information. It consists of two elements: a manifest, which is the metadata that describes information about the assembly and any resources it depends on; and a set of instructions in the form of Microsoft Intermediate Language (MSIL) code that is executed when the assembly is referenced.
You can group assembly elements into a single file assembly, which incorporates the manifest into a portable executable (PE) file, which can be an .EXE or .DLL, with the source code. You also can create a multifile assembly consisting of modules of compiled code, resources, or other files required by the application. In a multifile assembly, the manifest can be a standalone file or it can be incorporated into one of the PE files in the assembly.
When you add a .NET assembly to an installation, Wise for Windows Installer creates entries in the MsiAssembly and MsiAssemblyName tables.
See Assemblies in the Windows Installer SDK Help.
How does .NET reduce file sharing conflicts?
An important benefit of .NET installations is the reduction of file sharing conflicts. With the common language runtime, the assembly is described by a manifest; the registry is no longer relied upon for storing and accessing the COM activation data. This allows components to be fully isolated from each other.
Assembly sharing is accomplished in a number of ways:
To install .NET assemblies that are intended to be shared by many applications on the computer, make sure they are strongly named and install them into the Global Assembly Cache, which is a machine-wide code cache. Do not install assemblies into the Global Assembly Cache unless they specifically need to be shared. The Global Assembly Cache is available only if the .NET Framework is installed on the destination computer.
To safely share COM or Win32 assemblies among multiple applications and to minimize .DLL conflicts, use side-by-side assembly sharing. Instead of having a single version of an assembly that assumes backward compatibility with all applications, side-by-side assembly sharing enables multiple versions of a COM or Win32 assembly to run simultaneously on the system. Side-by-side assembly sharing is available only on Windows XP or later. See Side-by-Side Assemblies in the Windows Installer SDK Help.
To reserve a Win32 assembly for the exclusive use of one application, install it in a folder private to the application, typically the application directory. This is called a private assembly. The dependency of the application on the private assembly is specified in an application manifest file. On operating systems earlier than Windows XP, a copy of the private assembly and a .local file is installed into a private folder for the exclusive use of the application. A version of the assembly is also globally registered on the system and made available for any application that binds to it. The global version of the assembly can be the version installed with the application or an earlier version.
I thought .NET meant I could use XCOPY to install applications without registration. Why do I need to build a Windows Installer installation?
For a .NET application that uses only managed code and private assemblies, the installation process can be as simple as copying files to the destination computer. Most developers, however, will still need to create a compressed, single-file installation that is easy to deploy and that provides a friendly interface to the end user.
.NET applications that use shared assemblies, or that have a mix of managed and unmanaged code, cannot be installed via XCOPY. You should use the Windows Installer service for installations that do any of the following:
Install COM files
Install assemblies to the Global Assembly Cache
Require user information during the installation
Require security
Create a shortcut
Require elevated privileges to install on a locked-down computer
By creating a Windows Installer installation for your .NET applications, you can take advantage of the services Windows Installer provides: installation, repair, and removal of assemblies; roll back; install-on-demand; patching; and advertisement.
How does Wise for Windows Installer support .NET installations?
Wise for Windows Installer lets you install .NET assemblies into the Global Assembly Cache, or as side-by-side or private assemblies. It also lets you create mixed installations by registering .NET assemblies with COM.
If the .NET Framework is installed on your computer, Wise for Windows Installer can automate the process as follows:
Find all files in multifile assemblies and add them to the installation.
Scan for assembly dependencies and add them to the installation.
Determine attributes for registering the assembly files and add them to the MsiAssemblyName table.
Add registry keys for COM interop.
This article (taken from the "Microsoft .NET FAQs" help topic in Wise for Windows Installer and the Windows Installer Editor) answers questions about Microsoft .NET and defines important concepts you should understand before you use Wise for Windows Installer or the Windows Intsaller Editor to build .NET installations.
Answer
What does the common language runtime do?
The common language runtime manages the execution of code and provides services such as cross-language integration, code access security, object lifetime management, and debugging and profiling support. See Common Language Runtime in the MSDN Library.
What's the difference between managed and unmanaged code?
Code developed with a language compiler that targets the common language runtime is called managed code. All code based on Microsoft intermediate language (MSIL) executes as managed code. Managed code is self-describing; it contains metadata that describes every element managed by the common language runtime. The runtime uses the metadata to provide services.
Code that runs outside the runtime and does not contain metadata is called unmanaged code. Examples of unmanaged code are COM components, ActiveX interfaces, and Win32 API functions. Unmanaged code executes in the common language runtime environment with minimal services.
I don't want to rewrite all my applications as managed code. Can I add managed code to an existing application?
Few developers will be able to rewrite existing applications completely as managed (.NET) code. Instead, you can combine managed and unmanaged components in one installation. Code that contains a mix of managed and unmanaged elements is called interoperable code.
The common language runtime supports COM interoperability (interop). For backward compatibility, COM interop provides access to existing COM components without requiring you to modify the original components. COM interop also enables your COM clients to access managed code as easily as they access other COM objects. This is accomplished by adding information to the system registry so .NET components are called as though they were COM components. At runtime, the common language runtime marshals data between COM objects and managed objects as needed.
See Interoperating with Unmanaged Code in the MSDN Library.
What is an assembly?
An assembly is the primary building block of a .NET application. An assembly contains its own naming, binding, versioning, deployment, and configuration information. It consists of two elements: a manifest, which is the metadata that describes information about the assembly and any resources it depends on; and a set of instructions in the form of Microsoft Intermediate Language (MSIL) code that is executed when the assembly is referenced.
You can group assembly elements into a single file assembly, which incorporates the manifest into a portable executable (PE) file, which can be an .EXE or .DLL, with the source code. You also can create a multifile assembly consisting of modules of compiled code, resources, or other files required by the application. In a multifile assembly, the manifest can be a standalone file or it can be incorporated into one of the PE files in the assembly.
When you add a .NET assembly to an installation, Wise for Windows Installer creates entries in the MsiAssembly and MsiAssemblyName tables.
See Assemblies in the Windows Installer SDK Help.
How does .NET reduce file sharing conflicts?
An important benefit of .NET installations is the reduction of file sharing conflicts. With the common language runtime, the assembly is described by a manifest; the registry is no longer relied upon for storing and accessing the COM activation data. This allows components to be fully isolated from each other.
Assembly sharing is accomplished in a number of ways:
To install .NET assemblies that are intended to be shared by many applications on the computer, make sure they are strongly named and install them into the Global Assembly Cache, which is a machine-wide code cache. Do not install assemblies into the Global Assembly Cache unless they specifically need to be shared. The Global Assembly Cache is available only if the .NET Framework is installed on the destination computer.
To safely share COM or Win32 assemblies among multiple applications and to minimize .DLL conflicts, use side-by-side assembly sharing. Instead of having a single version of an assembly that assumes backward compatibility with all applications, side-by-side assembly sharing enables multiple versions of a COM or Win32 assembly to run simultaneously on the system. Side-by-side assembly sharing is available only on Windows XP or later. See Side-by-Side Assemblies in the Windows Installer SDK Help.
To reserve a Win32 assembly for the exclusive use of one application, install it in a folder private to the application, typically the application directory. This is called a private assembly. The dependency of the application on the private assembly is specified in an application manifest file. On operating systems earlier than Windows XP, a copy of the private assembly and a .local file is installed into a private folder for the exclusive use of the application. A version of the assembly is also globally registered on the system and made available for any application that binds to it. The global version of the assembly can be the version installed with the application or an earlier version.
I thought .NET meant I could use XCOPY to install applications without registration. Why do I need to build a Windows Installer installation?
For a .NET application that uses only managed code and private assemblies, the installation process can be as simple as copying files to the destination computer. Most developers, however, will still need to create a compressed, single-file installation that is easy to deploy and that provides a friendly interface to the end user.
.NET applications that use shared assemblies, or that have a mix of managed and unmanaged code, cannot be installed via XCOPY. You should use the Windows Installer service for installations that do any of the following:
Install COM files
Install assemblies to the Global Assembly Cache
Require user information during the installation
Require security
Create a shortcut
Require elevated privileges to install on a locked-down computer
By creating a Windows Installer installation for your .NET applications, you can take advantage of the services Windows Installer provides: installation, repair, and removal of assemblies; roll back; install-on-demand; patching; and advertisement.
How does Wise for Windows Installer support .NET installations?
Wise for Windows Installer lets you install .NET assemblies into the Global Assembly Cache, or as side-by-side or private assemblies. It also lets you create mixed installations by registering .NET assemblies with COM.
If the .NET Framework is installed on your computer, Wise for Windows Installer can automate the process as follows:
Find all files in multifile assemblies and add them to the installation.
Scan for assembly dependencies and add them to the installation.
Determine attributes for registering the assembly files and add them to the MsiAssemblyName table.
Add registry keys for COM interop.
13 April 2006
12 April 2006
Package server Security, Installer, and Collection Definition Hotfix
Problem
Section 1—Summary
This update, when installed on Notification Server SP3, replaces the existing Package Server Agent package. Package Servers in your environment need to be upgraded to this version for any update changes to apply. This update contains the following:
· Install, upgrade, and uninstall of Package Server Agent through Wise Installer. This was previously performed by Installshield.
· Registry key added to control whether or not the Package Server Agent can manage/change the security on its package directories.
· All Windows Computer requiring Altiris Package Server Agent Upgrade collection updated to only include Package Servers with Altiris Agent build 6.0.2338 (SP3), or greater.
Section 2—Installation
Name: Notification Server 6.0 SP3 Update 17613
Prerequisite software:
· NS build 6.0 SP3 Version 6.0.6074.
· Altiris Agent SP3 Version 6.0.2338 installed on Package Server.
IMPORTANT: The updated Package Server is not compatible with Altiris Agent versions earlier than 6.0.2338.
2.1—Install the Update
1. Download ftp://ftp2.altiris.com/Download/KB17613/Altiris_NS_6_0_SP3_KB17613.exe
to your Notification Server.
2. Run Altiris_NS_6_0_SP3_KB17613.exe.
2.2—Uninstall the Update
If, for any reason, you need to uninstall the update, the Notification Server will restore the original SP3 version of the Package Server Agent package. You can remove this via the ADD/REMOVE Programs option in the Control Panel on the Notification Server.
IMPORTANT: All updated Package Server Agents rolled out must be uninstalled before uninstalling the update on the Notification Server.
2.3—Upgrading Package Servers
The All Windows Computer Requiring Altiris Package Server Agent Upgrade collection that applies, by default, to the Windows Package Server Agent upgrade task, will not contain Package Servers with an Altiris Agent version lower than 6.0.2338 (SP3). Once the Altiris Agent has been upgraded on the Package Server, they will appear in this collection.
When the Windows Package Server Agent upgrade task is run, the upgrade will take approximately 15–20 seconds. Do not be concerned if the Altiris Agent does not start back up immediately after the upgrade task has run; this pause is expected.
Note: If the Package Server Agent is accidentally upgraded before the Altiris Agent, (which may happen if you are using a collection other than the All Windows Computer Requiring Altiris Package Server Agent Upgrade collection) the Altiris Agent and Package Server will not function or run Software Delivery tasks until the Altiris Agent has been upgraded to the required version. To do this, go to the Altiris Agent Installation page on the Notification Server and push out the Altiris Agent to the computer. This will carry out an upgrade of the installed Altiris Agent, and both the Altiris Agent and Package Server will then function normally.
Section 3—New Features and Enhancements in this Update
3.1—Package Server using Wise Installer
The install, upgrade and uninstall of the Package Server Agent is now done by Wise Installer; it was previously done by Installshield. There is a known issue with Installshield Version 10.5 that causes installations to fail on some systems with terminal services enabled with the following error message:
An Error (-5006 : 0x80004005) has occurred while running the setup. Please make sure you have finished any previous setups and closed other applications. If the error still occurs, please contact your vendor: Altiris.
For information, see http://community.installshield.com/showthread.php?threadid=109023
3.2—Package Server Agent Upgrade Collection
The Windows Computers requiring Altiris Package Server Agent Upgrade collection that applies, by default, to the Windows Package Server Agent Upgrade Software Delivery task has been modified.
Previously, the collection didn’t check for Altiris Agent Version 6.0.2338 (SP3) or higher. This resulted in the SP2 Altiris Agent Version 6.0.1508 being eligible for the SP3 Package Server Agent Upgrade. The SP3 Package Server Agent requires an installed Altiris Agent Version SP3, so, if the Package Server Agent is upgraded before the Altiris Agent then both will be unusable.
3.3 — New Registry key for disabling Package Server directory security
A new Package Server registry key, EnableDACLManagement, has been created to allow you to change how a Package Server manages the security on its packages.
By default, a Package Server manages its packages by setting specific permissions on package directories; this includes overriding any custom permissions you may have set on the directories. When this registry key is activated, Package Server will no longer override existing permissions on package directories.
Take care when using this key as incorrect permissions could potentially render the Package Server directories inaccessible to the Package Server and Altiris Agents.
To ensure a fully functional Package Server, full control for Local Administrator and System need to exist on all package directories in addition to any other custom permissions.
Normally, Altiris Agents and other Package Servers access the packages located on the Package Server computer using the Agent Connectivity Credential (ACC), configured on the Notification Server. To ensure they continue to download packages, configure the Everyone or ACC account with read and execute privileges on the package directories. This is required because when the key is activated, Package Server is instructed not to manage permissions, which includes not applying the ACC or Everyone account to the downloaded packages.
To create the Registry Key
As the registry key does not exist on a default install of the updated Package Server, create the DWORD key, 'EnableDACLManagement' under the following location in the registry—HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\Package Server. Before creating the key, stop the Altiris Agent Service and restart when finished.
The registry key can have one of the following settings:
· 0—Ensures that Package Server will not change existing security on package directories.
· 1—Will cause Package Server to function as normal by applying and resetting permissions on package directories.
--------------------------------------------------------------------------------
Environment
Notification Server 6.0 SP3 version 6.0.6074
Altiris Agent required—SP3 version 6.0.2338
The updated Package Server is not compatible with Altiris agent versions earlier than 6.0.2338
Cause
Software bug.
Resolution
This update, when installed on Notification Server SP3, replaces the existing Package Server Agent package, with an updated version. Package Servers within your environment will need to be upgraded to this version for any changes contained in the update to apply. Uninstalling the update on the Notification Server will restore the original SP3 version of the Package Server Agent package that existed prior to installing the update.
Important: Before upgrading your Package Servers to this updated version you must upgrade the Altiris Agent on your Package Servers to SP3 version 6.0.2338. The collection All Windows Computer Requiring Altiris Package Server Agent Upgrade, which applies by default to the Windows Package Server Agent upgrade task, will not contain Package Servers where the Altiris Agent version is lower than 6.0.2338 (SP3). Once the Altiris Agent has been upgraded on the Package Server, they will appear in this collection.
Section 1—Summary
This update, when installed on Notification Server SP3, replaces the existing Package Server Agent package. Package Servers in your environment need to be upgraded to this version for any update changes to apply. This update contains the following:
· Install, upgrade, and uninstall of Package Server Agent through Wise Installer. This was previously performed by Installshield.
· Registry key added to control whether or not the Package Server Agent can manage/change the security on its package directories.
· All Windows Computer requiring Altiris Package Server Agent Upgrade collection updated to only include Package Servers with Altiris Agent build 6.0.2338 (SP3), or greater.
Section 2—Installation
Name: Notification Server 6.0 SP3 Update 17613
Prerequisite software:
· NS build 6.0 SP3 Version 6.0.6074.
· Altiris Agent SP3 Version 6.0.2338 installed on Package Server.
IMPORTANT: The updated Package Server is not compatible with Altiris Agent versions earlier than 6.0.2338.
2.1—Install the Update
1. Download ftp://ftp2.altiris.com/Download/KB17613/Altiris_NS_6_0_SP3_KB17613.exe
to your Notification Server.
2. Run Altiris_NS_6_0_SP3_KB17613.exe.
2.2—Uninstall the Update
If, for any reason, you need to uninstall the update, the Notification Server will restore the original SP3 version of the Package Server Agent package. You can remove this via the ADD/REMOVE Programs option in the Control Panel on the Notification Server.
IMPORTANT: All updated Package Server Agents rolled out must be uninstalled before uninstalling the update on the Notification Server.
2.3—Upgrading Package Servers
The All Windows Computer Requiring Altiris Package Server Agent Upgrade collection that applies, by default, to the Windows Package Server Agent upgrade task, will not contain Package Servers with an Altiris Agent version lower than 6.0.2338 (SP3). Once the Altiris Agent has been upgraded on the Package Server, they will appear in this collection.
When the Windows Package Server Agent upgrade task is run, the upgrade will take approximately 15–20 seconds. Do not be concerned if the Altiris Agent does not start back up immediately after the upgrade task has run; this pause is expected.
Note: If the Package Server Agent is accidentally upgraded before the Altiris Agent, (which may happen if you are using a collection other than the All Windows Computer Requiring Altiris Package Server Agent Upgrade collection) the Altiris Agent and Package Server will not function or run Software Delivery tasks until the Altiris Agent has been upgraded to the required version. To do this, go to the Altiris Agent Installation page on the Notification Server and push out the Altiris Agent to the computer. This will carry out an upgrade of the installed Altiris Agent, and both the Altiris Agent and Package Server will then function normally.
Section 3—New Features and Enhancements in this Update
3.1—Package Server using Wise Installer
The install, upgrade and uninstall of the Package Server Agent is now done by Wise Installer; it was previously done by Installshield. There is a known issue with Installshield Version 10.5 that causes installations to fail on some systems with terminal services enabled with the following error message:
An Error (-5006 : 0x80004005) has occurred while running the setup. Please make sure you have finished any previous setups and closed other applications. If the error still occurs, please contact your vendor: Altiris.
For information, see http://community.installshield.com/showthread.php?threadid=109023
3.2—Package Server Agent Upgrade Collection
The Windows Computers requiring Altiris Package Server Agent Upgrade collection that applies, by default, to the Windows Package Server Agent Upgrade Software Delivery task has been modified.
Previously, the collection didn’t check for Altiris Agent Version 6.0.2338 (SP3) or higher. This resulted in the SP2 Altiris Agent Version 6.0.1508 being eligible for the SP3 Package Server Agent Upgrade. The SP3 Package Server Agent requires an installed Altiris Agent Version SP3, so, if the Package Server Agent is upgraded before the Altiris Agent then both will be unusable.
3.3 — New Registry key for disabling Package Server directory security
A new Package Server registry key, EnableDACLManagement, has been created to allow you to change how a Package Server manages the security on its packages.
By default, a Package Server manages its packages by setting specific permissions on package directories; this includes overriding any custom permissions you may have set on the directories. When this registry key is activated, Package Server will no longer override existing permissions on package directories.
Take care when using this key as incorrect permissions could potentially render the Package Server directories inaccessible to the Package Server and Altiris Agents.
To ensure a fully functional Package Server, full control for Local Administrator and System need to exist on all package directories in addition to any other custom permissions.
Normally, Altiris Agents and other Package Servers access the packages located on the Package Server computer using the Agent Connectivity Credential (ACC), configured on the Notification Server. To ensure they continue to download packages, configure the Everyone or ACC account with read and execute privileges on the package directories. This is required because when the key is activated, Package Server is instructed not to manage permissions, which includes not applying the ACC or Everyone account to the downloaded packages.
To create the Registry Key
As the registry key does not exist on a default install of the updated Package Server, create the DWORD key, 'EnableDACLManagement' under the following location in the registry—HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\Package Server. Before creating the key, stop the Altiris Agent Service and restart when finished.
The registry key can have one of the following settings:
· 0—Ensures that Package Server will not change existing security on package directories.
· 1—Will cause Package Server to function as normal by applying and resetting permissions on package directories.
--------------------------------------------------------------------------------
Environment
Notification Server 6.0 SP3 version 6.0.6074
Altiris Agent required—SP3 version 6.0.2338
The updated Package Server is not compatible with Altiris agent versions earlier than 6.0.2338
Cause
Software bug.
Resolution
This update, when installed on Notification Server SP3, replaces the existing Package Server Agent package, with an updated version. Package Servers within your environment will need to be upgraded to this version for any changes contained in the update to apply. Uninstalling the update on the Notification Server will restore the original SP3 version of the Package Server Agent package that existed prior to installing the update.
Important: Before upgrading your Package Servers to this updated version you must upgrade the Altiris Agent on your Package Servers to SP3 version 6.0.2338. The collection All Windows Computer Requiring Altiris Package Server Agent Upgrade, which applies by default to the Windows Package Server Agent upgrade task, will not contain Package Servers where the Altiris Agent version is lower than 6.0.2338 (SP3). Once the Altiris Agent has been upgraded on the Package Server, they will appear in this collection.
11 April 2006
Unable to get the config XML for the specified item (With DeleteAnItem.cs as stext)
Orphaned objects in the database will cause these messages. The GUIDs displayed in the log errors frequently point to the "Software Deliver Agent Install" object and have been traced to uninstalling and then reinstalling Software Delivery and the "Software Deliver Agent Install" object not properly being removed.
--------------------------------------------------------------------------------
Resolution
Complete the following:
To remove an orphaned object from the Notification Server tree use the following script:
nscript.exe deleteanitem.cs
and this will delete the object associated with this GUID. Always validate the GUID before removing it. This can be done by the following steps:
a. Open SQL Query Analyzer.
b. Make sure that you select the correct database, i.e. Altiris.
c. Type the following: select * from vitem where guid like ''
If it does not show, then go ahead and complete step 1.
Note: The nscript.exe file is found on the Notification Server in ...\program files\altiris\notification server\bin. The deleteanitem.cs file must be created and the blue part at the end of this article must be pasted in that file.
(Optional) If the script in step 1 does not remove the NS tree object, then there is likely an association that needs to be removed. This can be done with the following script:
delete from ItemReference where hint = 'policyappliestocollection' and ParentItemGuid =
this is DeleteAnItem.cs (Copy and paste the code)
using System;
using System.IO;
using Altiris.NS.ItemManagement;
using Altiris.NS.Security;
class MyScriptClass
{
static void Main( string[] args )
{
//
// Set the context for the current user
//
SecurityContextManager.SetContextData();
Guid itemGuid = Guid.Empty;
try
{
itemGuid = new Guid( args[ 0 ] );
}
catch( FormatException )
{
throw new ApplicationException( "Must pass a GUID as an argument" );
}
//
// Get the collection item
//
IItem itemToExport = Item.GetItem( itemGuid ) ;
if( null == itemToExport )
throw new ApplicationException( "The GUID does not match an item" );
itemToExport.Delete();
//
// Export the item
//
}
}
--------------------------------------------------------------------------------
Resolution
Complete the following:
To remove an orphaned object from the Notification Server tree use the following script:
nscript.exe deleteanitem.cs
and this will delete the object associated with this GUID. Always validate the GUID before removing it. This can be done by the following steps:
a. Open SQL Query Analyzer.
b. Make sure that you select the correct database, i.e. Altiris.
c. Type the following: select * from vitem where guid like '
If it does not show, then go ahead and complete step 1.
Note: The nscript.exe file is found on the Notification Server in ...\program files\altiris\notification server\bin. The deleteanitem.cs file must be created and the blue part at the end of this article must be pasted in that file.
(Optional) If the script in step 1 does not remove the NS tree object, then there is likely an association that needs to be removed. This can be done with the following script:
delete from ItemReference where hint = 'policyappliestocollection' and ParentItemGuid =
this is DeleteAnItem.cs (Copy and paste the code)
using System;
using System.IO;
using Altiris.NS.ItemManagement;
using Altiris.NS.Security;
class MyScriptClass
{
static void Main( string[] args )
{
//
// Set the context for the current user
//
SecurityContextManager.SetContextData();
Guid itemGuid = Guid.Empty;
try
{
itemGuid = new Guid( args[ 0 ] );
}
catch( FormatException )
{
throw new ApplicationException( "Must pass a GUID as an argument" );
}
//
// Get the collection item
//
IItem itemToExport = Item.GetItem( itemGuid ) ;
if( null == itemToExport )
throw new ApplicationException( "The GUID does not match an item" );
itemToExport.Delete();
//
// Export the item
//
}
}
DS Console slow?
From Microsoft KB article:http://support.microsoft.com/kb/296264/
By default, opportunistic locking is enabled for server message block
(SMB) clients that run one of the Windows operating systems that is
listed at the beginning of this article. Opportunistic locking allows
clients to lock files and locally cache information without the risk of
another user changing the file. This increases performance for many file
operations but may decrease performance in other operations because the
server that grants the opportunistic lock must manage the breaking of
that lock when another user requests access to the file.
On dedicated servers running Windows 2000 Professional, Server, Advanced
Server, or Windows XP Professional, create the following
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parame
ters
Create the following:
Value Name: EnableOplocks
Data Type: REG_DWORD
Parameter Value: 0 Hex (False)
(If your server is not a dedicated server you will also need to create
the workstation keys listed below.)
On workstations with Windows 2000 Professional, or Windows XP
Professional, in this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\P
arameters
Create the following:
Value Name: UseLockReadUnlock
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Value Name: UseOpportunisticLocking
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Value Name: UtilizeNtCaching
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Reboot all servers and clients affected
REF : Forum
By default, opportunistic locking is enabled for server message block
(SMB) clients that run one of the Windows operating systems that is
listed at the beginning of this article. Opportunistic locking allows
clients to lock files and locally cache information without the risk of
another user changing the file. This increases performance for many file
operations but may decrease performance in other operations because the
server that grants the opportunistic lock must manage the breaking of
that lock when another user requests access to the file.
On dedicated servers running Windows 2000 Professional, Server, Advanced
Server, or Windows XP Professional, create the following
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parame
ters
Create the following:
Value Name: EnableOplocks
Data Type: REG_DWORD
Parameter Value: 0 Hex (False)
(If your server is not a dedicated server you will also need to create
the workstation keys listed below.)
On workstations with Windows 2000 Professional, or Windows XP
Professional, in this key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanWorkstation\P
arameters
Create the following:
Value Name: UseLockReadUnlock
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Value Name: UseOpportunisticLocking
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Value Name: UtilizeNtCaching
Data Type: REG_DWORD
Parameter Value: 0 Hex (Disabled)
Reboot all servers and clients affected
REF : Forum
07 April 2006
License Removal Tool not working for NS6.0 SP3
[quote]--------------------------------------------------------------------------------
Problem
The License Removal Tool is not working to remove licenses (in NS6.0 SP3) that were installed in SP2 before the upgrade to SP3.
--------------------------------------------------------------------------------
Environment
NS 6.0 SP3
--------------------------------------------------------------------------------
Cause
The naming of the licenses have changed from Computing Edge to Altiris Licensing. The license removal tool has a static pointer to the Computing Edge certificates and does not detect the new storage location of licenses with SP3.
--------------------------------------------------------------------------------
Resolution
This has been reported as a bug for the license removal tool.
Workaround:
To manually remove licenses without the license removal tool, you can perform the following steps:
1- Start > Run > MMC.
2- Choose File > Add/Remove Snap-in.
3- Choose Add and highlight Certificates, then click Add.
4- Choose the radio button for " Computer account" , then click next.
5- Leave the default of " Local computer: .." , and click finish.
6- Close the Add Snap-in dialog box.
7- Click ok to apply the settings.
8- Highlight the Certificates folder under the Altiris Licensing to see the installed certificates.
If you remove all license certificates in this window, it will remove all licensing from the Notification Server similar to the way the license removal tool did. If you do not need to remove everything, you can find a specific license that will need to be removed by opening each license certificate and viewing the details (see below):
**Note: Once the licenses have been removed from the Microsoft Certificate Store, you will need to refresh the licensing page within the Notification Server for the results to show.
[/quote]
Problem
The License Removal Tool is not working to remove licenses (in NS6.0 SP3) that were installed in SP2 before the upgrade to SP3.
--------------------------------------------------------------------------------
Environment
NS 6.0 SP3
--------------------------------------------------------------------------------
Cause
The naming of the licenses have changed from Computing Edge to Altiris Licensing. The license removal tool has a static pointer to the Computing Edge certificates and does not detect the new storage location of licenses with SP3.
--------------------------------------------------------------------------------
Resolution
This has been reported as a bug for the license removal tool.
Workaround:
To manually remove licenses without the license removal tool, you can perform the following steps:
1- Start > Run > MMC.
2- Choose File > Add/Remove Snap-in.
3- Choose Add and highlight Certificates, then click Add.
4- Choose the radio button for " Computer account" , then click next.
5- Leave the default of " Local computer: .." , and click finish.
6- Close the Add Snap-in dialog box.
7- Click ok to apply the settings.
8- Highlight the Certificates folder under the Altiris Licensing to see the installed certificates.
If you remove all license certificates in this window, it will remove all licensing from the Notification Server similar to the way the license removal tool did. If you do not need to remove everything, you can find a specific license that will need to be removed by opening each license certificate and viewing the details (see below):
**Note: Once the licenses have been removed from the Microsoft Certificate Store, you will need to refresh the licensing page within the Notification Server for the results to show.
[/quote]
Subscribe to:
Posts (Atom)