DS 6.9 SP1 features

Introduction

Deployment Solution 6.9 SP1 software helps reduce the cost of deploying and managing servers, desktops, notebooks, and thin clients from a centralized location in your environment. It's an easy-to-use, automated deployment solution that offers OS deployment, configuration, PC personality migration, and software deployment across different hardware platforms and OS types. In SP1, we added support for Microsoft Windows Vista and Windows Server 2008, including running 32-bit applications on 64-bit platforms (WoW support).

The following are features of this release BUT still in BETA so not confirmed:

• Enhanced Vista 2008 management
• Updated WinPE installers
• Added that Deployment Solution now runs on Windows 2008 servers
• Added support for 64-bit servers (Wow 64)
• Added support for disabling and enabling NICs (network interface card)
• Added SQL 2008 support
• Added that DAgent now supports remote control
• Added that DAgent is now the default agent for Windows clients
• Added support for UNC imaging
• Added a sample job for upgrading AClient to DAgent
• Enhanced rip and replace to specify the jobs that are replayed
• Enhanced user rights
  • View only the computers and jobs that you have the rights to manage
  • Limit access to master return codes

How to check the status (active, retired , etc) of a machine?

1. You change/view the status of a computer under Altiris Console, click the Resources tab > Resources > Defaults.

2. Import the attached report into the reports tab or create your own using SQL like the following. that can help to identify retired machines.
Run it against Altiris database. ( replace 'retired' to the status you want to check).

SELECT     i1.Name AS Asset, rt.Name AS [resource type], i2.Name AS
Status, i1.Guid
FROM         ResourceAssociation ra INNER JOIN
                      Item i1 ON i1.Guid = ra.ParentResourceGuid INNER
JOIN
                      Item i2 ON i2.Guid = ra.ChildResourceGuid INNER
JOIN
                      ItemResource ir ON ra.ParentResourceGuid = ir.Guid
INNER JOIN
                      ResourceType rt ON rt.Guid = ir.ResourceTypeGuid
WHERE     (ra.ResourceAssociationTypeGuid =
'3028166F-C0D6-41D8-9CB7-F64852E0FD01') AND (i2.Name LIKE 'retired')

After running AD Import, new computers don't appear under active collections or OU collections

Problem/Symptoms

AD Import is not importing all computers. Some computers were added about four or five weeks ago in the Network.
The Altiris Agent was installed on the new computers. Then, those new computers were added in the AD domain.
AD Import (Full Import) is run but the new computers are not being imported into Notification Server via AD Import.

The Altiris Log Viewer does show that the AD Import found those computers when Trace was enabled in the Log Viewer.
However, these computers are not being populated into the OUs collections or All Computers collection.

---

Environment

Notification Server 6.0.6074 SP3 + R*
Active Directory Connector 6.1.842
AD Connector Hotfix 3 (KB34704)

---

Cause

Verified the status for those machines. The computer names were used in the past and then retired. These client machines were built over the last few months but the names were previously used sometime last year then decommissioned.  Their Purging maintenance is set to 1 month and to Retire only.
The computer names are being re-used.  The GUID is then created based on the name and domain so they are the same as the previous retired computer names.

---

Resolution

Find the computer in a report or in the Altiris Console by clicking the Resources tab > Resources > Defaults.
Right-click the row the computer is listed on, click Set Asset Status, and select the wanted status. (In this case it was changed from "Retired" to "Active".)

As well, you can create your own report to identify what computers are set to Retired. See Article ID: 24473 "How to check the status (active, retired , etc) of a machine?" as example.

Beta II CMS Installation Error on PCANYWhere

Error 1603 on PCAnyWhere during installation of Beta Refresh II

You need to do 2 things

1) create a Group Policy when on a domain or a Local Policy on a standalone:

Computer Configuration > Windows Settings > Security Settings > Software Restriction Policies (if there isn't one, create one), Right Pane, Double-click Enforcement, change bottom radio button to All users except local administrators

2) Run then MS KB 925336

If you are NOT on a Domain and use Local Policy then this is the regkey to check:

Open HKLM\Software\Policies\Microsoft\windows\safer\codeidentifiers and see if there is a DWord entry called "PolicyScope". If it's not there, create it, and set the value to 1.

Thx to Beta Forum thread : Beta Forum