Video Screencast Help
Endpoint Management Community Blog
Showing posts in English
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 [...

Mauro Dalvit | 21 Nov 2014 | 1 comment

We already explained how to mount and un-mount boot.wim:

https://www-secure.symantec.com/connect/blogs/ds-7x-mounting-bootwim-file-access-folder-structure-enable-checkaddremove-files-and-folders

In this post, we will go through the process of manually injecting x86 drivers for the network card Intel i217 i218 into boot.wim

1 - First of all we need to prepare the Driver's Folder by cleaning up all the unecessary drivers/files

See how to pick the correct driver for a specific NIC:

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

and how to do the clean-up please have a look at this article:

...

Mauro Dalvit | 21 Nov 2014 | 2 comments

Please see below how to access the WinPE pre-boot file "boot.wim" in few simple steps.

We take as example a WinPe 4.0 Pre-Boot .ISO configuration created by using Bootwiz.exe following article below:

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

1 - Locate your newly created .ISO configuration:

120.jpg

2 - Mount the image using for example "magicISO"

121.jpg

4 - If not already present create anew folder in C:\  in our example we name it "test"

5 - Copy the boot.wim file from the mounted .iso image (E:\SOURCES) to the c:\test folder

6 - Create a...

Mauro Dalvit | 21 Nov 2014 | 0 comments

When creating bootable USB or .ISO with Bootwiz.exe, Ghost32.exe is not included in the boot.wim file (WinPe4.0 file)

bootwiz.exe is located here on the SMP:

\Program Files\Altiris\Deployment\BDC\bootwiz\BootWiz.exe

Please keep in mind that with a fresh install of DS 7.5 SP1 you need first to import the windows ADK for WinPE 4.0 by following wizard at:

settings(tab) ->deployment -> Create Preboot Configurations

1 - After importing and installing the WinPe 4.0 environment, please run bootwiz.exe and follow the wizard to create a bootable USB.

100_0.jpg

2 - Remember to select Stand-Alone boot:

110.jpg

3 - When the Pre-boot configuration creation process has completed, you will be able to access its folder structure from...

Network23 | 20 Nov 2014 | 0 comments

Hi Enpoint Management Community,

ITMS 7.5 SP1 HF4 is available via SIM!

Release Notes can be found here

Mikael Ulvesjö | 20 Nov 2014 | 0 comments

This is only a short guide to help you get started in compiling your own drivers or use my pre-compiled, the guide is written for some one who have prior linux and kernel compiling experience.

Required software:
A system that runs rhel server 6.4 i386 can be a vm on your local workstation.
Kernel sources and headers 2.6.32-358.el6 
gcc-4.3 the GNU C Compiler
make the tool that runs the compile script
wget a tool to download files from http servers
bzip2 a compression tool
build-essentials tools and libraries used to compile

Get the kernel config from you altiris server it's path should be something like c:\Program Files\Altiris\Notification Server\NSCap\bin\Deployment\BDC\bootwiz\Platforms\Linux\x86\Build\config.x86
copy the config.x86 file to your kernel source directory (mine is /usr/src/kernels/linux-2.6.32-358.el6)and rename it to .config and "make oldconfig" to solve any configuration problems.

...

Marcello D'Angelone | 18 Nov 2014 | 0 comments

Since Deployment Solution 7.5, computers rebooted to Automation are renamed to their serial numbers rather than "MiniNTxxxx".

To retrieve the computer serial number, while in automation, type on the command prompt:

"wmic bios get serialnumber"

Then lookup the computer on the console under Manage > Computers.

Instead of adding a Search custom criteria, that should help to quickly identify the target machine for troubleshooting purpose.