Dell Optiplex 755 and IBM T61 fails to see the hard drive and connect to Deployment Solution

Environment
Deployment Solution 6.8 SP2Windows PE* 1.5Dell Optiplex 755 with Intel Vpro NIC IBM T61
Intel VPro Certified 82566 DM-2

Cause
SATA controller is not being detected and NIC drivers are not loading.

Resolution
Follow these steps to get the latest drivers from dell for the SATA controller and VPro NIC then modify the WinPE boot:
1. Download the Intel Matrix Storage Manager drivers from here. For Linux download the AHCI drivers through boot disk creator using the internet option when specifying the Nic drivers in the wizard.
2. Follow steps 1–4 from article 19067.
3. Download the Intel 825xx Gigabit Platform LAN Network Device drivers from here. For Linux download the Intel e1000 drivers through boot disk creator using the internet option when specifying the Nic drivers in the wizard.
4. Create or modify a WinPE 32-bit boot (either through boot disk creator or PXE config).
5. Add the NIC driver (e1e5132.inf) and continue through the wizard until the "Boot Options Settings" page and select "factory -winpe" then finish to the end of the wizard.
6. Change the BIOS setting to SATA compatibility from AHCI in the T61 and T61P

VM to fast to switch to boot order?

Edit your .vmx file and add the line:
bios.bootDelay = "5000"
which adds a 5000 millisecond (5 second) delay to the boot,
**or add**
bios.forceSetupOnce = "TRUE"
to make the VM enter the BIOS setup at the next boot.
(Thx Michael)

What is the AexAgentUIHost.exe process?

This process hosts the system tray icon for those computers logged onto the NS via terminal services. In addition, you will see one instance of this process for each user logged on to the system.

There is a registry key setting that can keep AexAgentUIHost.exe from loading for each user:

HKLM\Software\Altiris\Altiris Agent\Run UI in main Session only

Changing the value to 1 will keep the process from loading for every user.

Multiple instances of the same filename, but different file path are not reported by Inventory Solution for Windows

Problem/Symptoms

A Software Inventory scan using AeXAuditPls.exe does not report multiple instances of the same file. The Windows* operating system allows files to be named the same as long as they are in separate folders. As determined by inspecting the auditpls.nsi file on a client computer, files with the same name but different file paths are collected properly by AeXAuditPls.exe and sent to the Notification Server. However, only one of these files is added to the AeX SW Audit Software data class.

Cause

The Notification Server dataloader uses the following properties to determine a unique row to be placed into the AeX SW Audit Software data class (Inv_AeX_SW_Audit_Software_spt and Cmn_SW_Common tables in the database): Manufacturer Product Name Product Version Language File Name File Size InternalName File Description The dataloader will ignore multiple instances of files that match on these properties. Note that "File Path" in not used to determine uniqueness, which is why only one instance of a file that occurs in multiple folders is inserted into the database. Also note that since "File Size" is used to determine uniqueness, data files (and executable files) with the same name, but with different sizes, will be inserted into the database. On the odd chance that data files with the same name contain different data, but have the same exact size, only one file will be inserted into the database.

Resolution

This resolution is provided "as is" and has not been reviewed by the developers of Inventory Solution for Windows. It may not be suitable for every environment. Important: Because this resolution updates the data in the database, back up the Altiris database first. A change to the DataClassAttribute Table will cause the Data Loader to use "File Path" to determine unique rows to insert into the database. The following SQL query will show the attributes the Data Loader uses to determine uniqueness. USE Altiris SELECT * FROM DataClassAttribute WHERE InvClassId = (SELECT id FROM DataClass WHERE Name = 'AeX SW Audit Software') ORDER BY AttrId You can use this SQL statement to change the "File Path" attribute so it is used to determine uniqueness. USE Altiris UPDATE DataClassAttribute SET KeyIndex = AttrId, Nullable = 0 WHERE AttrName = 'File Path' AND InvClassId = (SELECT id FROM DataClass WHERE Name = 'AeX SW Audit Software') Note: This change may be overwritten if a upgrade or repair is made to Inventory Solution for Windows.

WINPE2.1, Deployment Server 6.9 and VMWare

ref : link to juice

As we prepare for a new deployment of Deployment Solution 6.9, IT personnel may encounter difficulties using WinPE 2.x in conjunction with VMWare network drivers. In addition, as more and more users try to virtualize their environments, Microsoft Vista users might find themselves without networking in VMWare Virtual Machines.
There is little known work-around for this issue: make the virtual machine load up the Intel e1000 network driver. Forcing this change will make virtual machines think they have an e1000 network driver and load up the network. This also prepares Virtual Machines to run automation jobs in a pre-boot environment using this driver instead of the VMWare drivers.

Note that the minimum requirement for WinPE 2.0 and 2.1 is 512 megs of ram. If you use less then that you may experience problems that are very similar to driver issues.

Also, in VMware 6.0 if you create a VM and specify it as a Vista machine it will automatically add the e1000 identifier to the nic.

Procedure to free up Patch Management License for Retired PC's

I used this procedure to free up my license on retired resource for Patch Management KB Ref

1. Create a folder in the Resource Tab, Resources
2. Get the GUID of this folder by right clicking on this folder then Properties and copy the GUID for later use
3. Get the Report from the KB link and import it into Reports
4. Run this report for Non Active Resources
5. Select All resource and move them to the newly created folder in step 1
6. Create a folder on the server where the exported files will reside
7. Open a command window and type \diagnostics\ImportExportUtil /export {GUID from step 2} ""
8. When export is complete check if all files are in this directory you created in step 6, if ok then continue.
9. return to your report from step 4, Select all Non Active resoures and delete them by right clicking and select Delete
10. Check the license by clicken refresh buttun in Configuration Tab, Licenses
11. Now reimport the deleted resources by run the following command in the command window on the command prompt \diagnostics\ImportExportUtil /import ""
12. Rerun the report from step 4 to check if all resources are back.

Example
E:\AExNS\Diagnostics\ImportExportUtil /export {21082ac4-26fe-43e9-a304-98632f65afa5} "e:\RetiredPC"
E:\AExNS\Diagnostics\ImportExportUtil /import "e:\RetiredPC"

KNOWN ISSUE: Deployment Server Win32 console security does not properly pass through authenticate users from AD groups

Problem/Symptoms

When the Deployment Server Win32 console security is enabled with imported AD group, and a user attempts to log into the console (using AD pass through authentication), they are prompted for credentials. If they do not enter the credentials it will open the console with no security rights. If they do enter in their proper credentials it opens the console with all security rights that the user should have. It also creates a new security user in the Deployment Solution console security instead of just using the group membership.

There are multiple types of environments that can cause this behavior. The following are 3 different known scenarios that exhibit this behavior:

Scenario 1

1. AD environment is set up as follows: There are two domain controllers, "parent.com", and "child.parent.com" which is a child domain of "parent.com".
2. A security group is added to "child.parent.com" domain called "Console Users".
3. A domain user is created called "Altiris" and is added to the "Console Users" group.
4. Deployment Solution 6.8 SP2 build 378 is installed with all default options.
5. Console security is enabled, and the "Console Users" AD group is given full administrative rights to the Deployment Solution console.
6. Log onto a computer that has a Win32 console installed using the account AD "Altiris" from the "child.parent.com" domain.
7. Notice how the console security prompts for the username and password. Enter that information and continue.
8. From the console select Tools > Security and notice how that user ("Altiris@child.parent.com") is now listed as a security user even though it was never added directly, but only through AD group membership.

Scenario 2

1. AD environment is set up as follows: There is one domain controller, "company.com", which was given a NETBIOS name of "MYCOMPANY" (which is different than the UPN domain name).
2. A security group is added to "company.com" domain called "Console Users".
3. A domain user is created called "Altiris" and is added to the "Console Users" group.
4. Deployment Solution 6.8 SP2 build 378 is installed with all default options.
5. Console security is enabled, and the "Console Users" AD group is given full administrative rights to the Deployment Solution console.
6. Log onto a computer that has a Win32 console installed using the account AD "Altiris" from the "company.com" domain.
7. Notice how the console security prompts for the username and password. Enter that information and continue.

Scenario 3

1. AD environment is set up as follows: There is one domain controllers, "company.com", which is set up with default settings (where the NETBIOS name is "COMPANY" which is default).
2. A security group is added to "company.com" domain called "Console Users".
3. The domain user "Administrator" is added to the "Console Users" group.
4. The domain user account of "Administrator" does not have the UPN name. Other accounts on the domain controller also might not have a UPN name, but have a SAM name.
5. Deployment Solution 6.8 SP2 build 378 is installed with all default options.
6. Console security is enabled, and the "Console Users" AD group is given full administrative rights to the Deployment Solution console.
7. Log onto a computer that has a Win32 console installed using the account AD "Administrator" from the "company.com" domain.
8. Notice how the console security prompts for the username and password. Enter that information and continue.
9. From the console select Tools > Security and notice how that user ("Administrator@") is now listed as a security user even though it was never added directly, but only through AD group membership.

________________________________

Environment

Deployment Solution 6.8 SP2 build 378
Using the Win32 console with security enabled with AD groups imported.

________________________________

Cause

The original express.exe from DS SP2 build 378 was incorrectly caching the NETBIOS domain name in the database. Because the users were cached incorrectly they were not being identified by Active Directory.

________________________________

Resolution

Solution:

1) Backup Express database and express.exe: Backup the database - usually named 'express' - before making any changes. Make a copy of express.exe.

2) Remove improperly cached users: Users who have attempted to login to the Deployment Console with security enabled prior to this fix will have users incorrectly cached in the database. These users must be removed from the securityuser table. To remove these users run the following query against the SQL server:

DELETE FROM securityuser WHERE ad_user = 1 AND user_guid = ''

3) Replace Express.exe: Replace the original express.exe included in SP2 with the express.exe attached to this knowledgebase article.

4) Appy License to Express.exe: Open the license tool under your Deployment Server program files directory. (License.exe) Run the tool to license the express.exe with all applicable licenses.

Note 1: This executable has been through the official Symantec Hotfix process and is supported by Symantec Support Services.

Note 2: No services need to be stopped to affect this change. Only verify that console users have closed any remote sessions to the console. For locally installed consoles, this exe will need to be deployed via DS or NS once licensed.

Note 3: Changes made to express.exe in KB 38727 are also included in the express.exe attached to this KB.

Carbon Copy Synchronous and Asynchronous Mode Technical Document

Synchronous mode is enabled after the Carbon Copy application is installed , and upon reboot the Carbon Copy remote-control driver (ccvideo4.dll) and a Carbon Copy device interceptor (ccdevice.sys) are installed and placed in the chain between the system video driver and the miniport driver. This driver and interceptor intercepts and evaluates the calls passed for processing. During an actual remote-control session , any changes that occur on the screen of the Carbon Copy clients are emulated back to the Carbon Copy console user on a synchronous line by line basis. So essentially, any object that changes on the client is painted simultaneously line by line in the console user's remote-control window.

Asynchronous mode does not utilize any remote-control driver's but interfaces with the Windows GDI. In this manner, blocks from the actual client's desktop are transmitted back to the console user's remote-control window.(64 x 32 default). This block transmission does not occur concurrently with the changes on the clients desktop so the appearance is a slight delay if you were to have the console and the client machine side-by-side.