Deployment and Imaging Group

After reinstalling a DS 6.9 sp6 on a new 2008 R2 server, upgrading from a copy the previous “express” base. We care reconfigure the “default settings” to the new IP for any new agent, to avoid losing the agent reconfiguring the older DS.

If installing a Dagent on Windows 7 x64: connected OK onto DS console sp6.

We build the WinPE 4.0, it’s connect correctly the new DS share express and load the Dagent.

Agent 6.9.648 x64, display a status “agent recorded”: on IP DS server is correct. But MAC address show empty on the “status view”. The DS console do not see appearing this client.

We try on different hardware, with preboot x64 and x86: and got the same issue!

Where can I find and activate agent logs on a preboot ?

Any body got the same ?

PS: Yes, the Firewall is OFF on server 2008 R2, and the WinPE generated does not activate the firewall option.

in PXElog_server.txt I got a lot of repeat of this information, seems from an axis box, but don't think related this issue

PxeLog_DSTraffic.Txt has no error

But I need to find the correct logs under the agent under WinPE, not PXE part :(

find a KB, but only talk about bootwork (DOS) ! all the same updated last in May 2013 :(

http://www.symantec.com/docs/HOWTO1018

I found an older one (HOWTO9302)

, talk about

• DAgent: %systemroot%\temp\dagent.log

 

I will try to see that.

I've got the exact same problem as Pascal.  I upgraded from DS 6.9 SP5 to SP6 and Windows PE 4.0.  Upon client reboot while executing a Windows PE load Windows PE connects back to the server, shows status as "Client Record Updated", the correct server and client IP address, but no MAC address.  The console shows the computer as being down.  Windows PE never reboots if there is no job to do and if there is an imaging job the console shows "booting to automation" and that is the end of it.  Nothing else happens.  The DOS window in Windows PE shows that it launches Dagent, "Calling Custom Actions", and "Startup complete" and then goes to the drive prompt.  Any suggestions are appreciated.

Hi Pascal, It's a long shot, but I remember having this issue a long time ago at a customer. Here specifically it was due to the WinPE images not having WMI scripting enabled (although this should be on by default). Because WMI was not enabled it could not get some parameters from the client. I thought this was also the mac address, but I'm can't remember the full picture here.. grtz, dawi_x

I recently encountered same problem with a customer. After some investigation we discovered that McAfee Antivirus was preventing the build process from adding the WMI components to the WinPE image. No errors appeared during build.

I suspected that WMI components were not added so I decided to mount the WIM-file and list the packages. I used the following commands:

DISM.exe /Mount-Wim /WimFile:"D:\Altiris\eXpress\Deployment Server\PXE\MasterImages\MenuOption169\X86pc\sources\boot.wim" /index:1 /MountDir:D:\Mountx86
DISM /image:D:\Mountx86 /get-packages

And then I tried manually to add the WMI components but this gave an access denied due to McAfee interfering. To manually add the WMI components I used the following commands.

DISM.exe /Mount-Wim /WimFile:"D:\Altiris\eXpress\Deployment Server\PXE\MasterImages\MenuOption169\X86pc\sources\boot.wim" /index:1 /MountDir:D:\Mountx86
dism /image:D:\Mountx86 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-WMI.cab"
dism /image:D:\Mountx86 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"
DISM.exe /Commit-Wim /MountDir:D:\Mountx86

 

 

LCode and dawi_x, you were both right no the money.  The WMI components were missing from the Windows PE 4.0 image due to a block by McAfee.  It's working great now.  Thanks so much!!!

I can confirm, without identifying the source, we replay the full installation, but care removing 1st the McAfee installation (temporary). We were also installing with a single service instead of using 2 differents (one installer, one for service). and reinstall a fresh base instead of upgrading previous existing...

And it was working. But with your feedbacl LCode, I got a confirmation about McAfee ;-) Thanks a lot.

Hello All,

 

We are also facing the same error and we tried to execute the same command which you provide but we are facing the error, as our DS 6.9 is installed in C:\Program Files (X86).

Kindly find the attachment of error for the same.

 

Thanks in advance....

Regards,

 

 

 

Please provide the DISM log file that is mentioned in the screenshot.

Hello SK,

 

Please find the attached DISM.log file.

 

Regards,

 

Hello All,

We are not able to understand what is happning ,we disabled all McAfee services on Server then edited WinPe and then for first time client show computer name and mac address but after that client system rebooted.

 After that we disable McAfee on client also now we are unable to boot the client system in automation and geting error saying "your pc ran into a problem and needs to restart we're just collecting some error info".

We update WinPe many time and created boot disk creater but we are now geting same error but after enabling McAfee it stated giving same problem of  display a status “agent recorded”: on IP DS server is correct. But MAC address show empty on the “status view”. The DS console do not see appearing this client.

Regards,

 

  

Hello All,

 

Awaiting for your reply......

 

Thanks in advance....

 

 

Hello Mahadev, Please remember that we are still in the holiday season and that the Forum is monitored by the community when they have time. If you require faster responses then please open a support case.

Hi, as I said, we do reinstall all the DS 6.9, WITHOUT installed MCAFEE client. Taking care to "pre-install" the ADK 8.0 on default Microsoft Path, and TO REBOOT the DS server BEFORE install it.

Take care Microsoft ADK is using temp folder on C drive also by default... So Disk space system is required to make it works correctly :(

So when install the WinPE4 preboot from DS we select the "already installed ADK" option.

On our site, this were solving our problem:

the empty MAC on Dagent view WinPE preboot, and not appearing on DS console.

 

Please notice we are using also an initial deploy job: and was needing to remove the "localized" DLL  (AexDS_FR.dll) to make it works correctly, as we got the following error in application Windows logs, all 6 seconds, instead of the initial deployment menu displaying:

The description for Event ID 3 from source Altiris Deployment Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Incorrect syntax near 'utilisateur'.

Unclosed quotation mark after the character string ''.

the message resource is present but the message is not found in the string/message table

"utilisateur" is the french word for "user", and probably a similar issue if using another language, in your own language (like utente, etc...)

Another bug: feel free to escalate to Symantec support, I enough loss a lot of time all those bugs, and don't proceed myself Symantec support case escalation because time consumming, except in this forum. A pity Symantec still wait a "case" escalation for their product improvement. Hope to take care this Forum to "act". Best regards all.

Oh, well, another one:

%ALTIRIS_PXE_SERVER%

does not initialize correctly under WinPE 4 (All %ALTIRIS_PXE* parameters not exist at all)

see the KB

http://www.symantec.com/docs/TECH213143

this one already documented ;-)

DISM is the start of each of the 4 commands. You ran all of the commands on the same line, which causes problems because DISM.EXE does not have DISM as an available variable. Here are the commands, modified for your C: drive installation, with separated lines.

DISM.exe /Mount-Wim /WimFile:"C:\Program Files (x86)\Altiris\eXpress\Deployment Server\PXE\MasterImages\MenuOption169\X86pc\sources\boot.wim" /index:1 /MountDir:C:\Mountx86

dism /image:C:\Mountx86 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-WMI.cab"

dism /image:C:\Mountx86 /add-package /packagepath:"C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"

DISM.exe /Commit-Wim /MountDir:C:\Mountx86