Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts in English
Mauro Dalvit | 05 Dec 2014 | 0 comments

In some case, after upgrading DS, the PECTAgent.exe is crashing in automation without any error message.

From the PECTAgent. logs we see as final lines:

"</resourcekeys>
</request>"

the PECTAgent.exe crashes and stops

Suspected cause of this is corrupted .dll components.

Compare the size of the .dll files below taken from a DS 7.5 SP1 HF4 environment:

PECTAgent.exe version: 7.5.3290.0

x86

\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x86\Base\Program Files\Symantec\Deployment

07822105.jpg

x64

\Program Files\Altiris\Deployment\BDC\bootwiz\oem\DS\winpe\x64\Base\Program Files\Symantec\Deployment

x64.jpg

It is possible that even .dll files having size as...

SK | 29 Nov 2014 | 1 comment

Hello all,

Now I know that some of you may class this as spam; however, as Raynet GmbH is a Symantec Partner, I believe that this is a worthy blog post. 

Starting on Monday 1st December 2014, Raynet GmbH will be offering discounts on our products, services & training classes in the form of an advent calender. 

Please visit our web site for further details on this great opportunity:-  https://raynet.de/Events/advent_calendar

Feel free to mention my name when you register for one or more of the upcoming offers. 

Marcello D'Angelone | 27 Nov 2014 | 0 comments

There are three ways to find this information:

1) From the SMP Console you can simply add the machine's resource GUID value at the end of the link below:
 
 
2) From the Console go to Manage > Computers search for the computer Name then Right-click, select
Resource Manager for that particular system, and go to Summaries > Filter Summary.
 
 
3) From SQL Server Management Studio
you can look at the CollectionMembership and connect this with item and/or vcomputer table, for example with the following query:
SELECT v.Name AS 'Computer Name', i.Name AS 'Filter Name', p.Name AS 'Solution', i.CreatedDate AS 'CreatedDate', i.ModifiedDate AS '...
Mauro Dalvit | 26 Nov 2014 | 0 comments

Collecting PECTAgent .dmp files in automation(WInPE4.0) environment:

1 - The app procexp.exe can be used to create PECTAgent dumps in automation, find it here and extract:

<SMPdrive>\Tools\Sysinternals\Processes_And_Threads\ProcessExplorerNt.zip

2 - Create a shared folder on the SMP with "local Admin" or "authenticated users" full permission

61.jpg

3 - in Automation create a share using the command prompt, for example:

X:\>net use q: \\<yourSMPname>\shared

60.jpg

4 - Run "procexp.exe" from Network location (q: in our example)

62.jpg
 

5 - Right click on...

Mauro Dalvit | 24 Nov 2014 | 0 comments

1 - To Download the Windows ADK for WinPE 4.0 please access the following link:

https://www.microsoft.com/en-in/download/details.aspx?id=30652

45.jpg

2 - Save adksetup.exe locally

3 - Run adksetup.exe and follow the installation wizard

4 - Select the Features you want to install (de-select the ones that are not needed):

46.jpg

5 - Complete installation

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help our tech community – Thank you, Mauro

Mauro Dalvit | 24 Nov 2014 | 0 comments

When running "boot to PXE" or "boot to automation" from the console, it is common to see this coming up on the client machine instead of WinPE:

39.jpg

This will result in a LOOP as the client will boot into Production and then the "boot to PXE" or "boot to automation" task will be picked up again until it times out.

Please check the BIOS Boot Setup; very likely "Network Boot" is NOT set as FIRST:

38.jpg

So to correct this, please modify to:

41.jpg

and the client should now boot into WinPE 4.0 as sequence below:

42_0.jpg

...

Mauro Dalvit | 24 Nov 2014 | 0 comments

If you are looking for "Ghost Boot Wizard" in DS 7.5, keep in mind that this name is associated with Ghost Solution Suite.

Iin Deployment Solution 7.5 a very similar tool is "Boot Disk Creator" (bootwiz.exe) and on the SMP it is located here:

\Program Files\Altiris\Deployment\BDC\bootwiz

37.jpg

If you want to know how to include Ghost tools to the USB/DVD pre-boot configuration please see article:

https://www-secure.symantec.com/connect/blogs/ds-75-how-include-ghost32exe-bootable-usb-or-iso-created-bootwizexe

If you are an expert Ghost user and you want to know the location of GHOST executables and tools in SMP 7.5, see below:

...

Mauro Dalvit | 24 Nov 2014 | 0 comments

If you are an expert GHOST user and you are looking for the following:

  • DeployAnywhere.exe
  • ghost32.exe
  • DriverDBMgr.exe
  • DriverManager.exe
  • Ghostexp.exe
  • GhostSrv.exe
  • DPInst.exe
  • + others...

They are located on the SMP at:

\Program Files\Altiris\Deployment\Imaging\ghost\x86

36.jpg

and x64 at:

\Program Files\Altiris\Deployment\Imaging\ghost\x64

NOTE:

If you found the above information useful, please give this article a thumbs-up(top right of the post) or add a comment below. Your feedback will help our tech community – Thank you, Mauro

Mauro Dalvit | 24 Nov 2014 | 0 comments

Introduction:

Preboot Drivers:

Using WinPE 4.0 as pre-boot environment we need Windows8 Drivers

DeployAnywhere drivers:

DeployAnywhere Drivers will always match the deployed(production) operating system - in this example Windows7

How To:

1 - Having the correct Driver Folder already downloaded as form article:

https://www-secure.symantec.com/connect/blogs/ds-75-how-pick-correct-driver-specific-nic

The folder will contain multiple drivers and also additional folders end executables:

29.jpg

2 - The pre-boot driver needed in our example is e1c6332, the folder will only need to contain the following:

...

Mauro Dalvit | 24 Nov 2014 | 0 comments

Introduction:

Preboot Drivers:

Using WinPE 4.0 as pre-boot environment we need Windows8 Drivers

DeployAnywhere drivers:

DeployAnywhere Drivers will always match the deployed(production) operating system - in this example Windows7

How To:

To start searching for the drivers we need a client machine, for example an out-of-the-box laptop/desktop with OS installed (Windows7 in our example).

1 - Plug the machine to the network so the NIC system information will get populated

2 - Run msinfo32.exe

25.jpg

3 - Browse to "Adapter"

26.jpg

4 - Collect:

  • NAME
  • PNP DEVICE ID
  • DRIVER

in our example:

(NIC)Name [...