Quantcast
Channel: Symantec Connect: Deployment and Imaging
Viewing all 645 articles
Browse latest View live

DS 7.5 - How to include ghost32.exe in a bootable USB or .ISO created with bootwiz.exe

$
0
0
Twitter Card Style: 
summary

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

 

bootwix.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 bootwiz as below:

111.jpg

 

Locate ghost32.exe here on the SMP:

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

4 - Now you can add ghost32.exe to the newly created pre-boot configuration by adding the file or folder to the file structure in bootwiz

(Right click to create a folder and to add the file)

112.jpg

 

5 - Please remember to re-create the preboot configuration(create boot disk)

113.jpg

 

6 - Save your .iso in a folder easily accessible or onto a USB or CD/DVD and remember to select "stand-alone boot" as on picture below:

115.jpg

 

Ghost32.exe is now included into the boot.wim file. After booting into WinPe4.0 you will be able to access Ghost32.exe by browsing the X:\ drive in automation

 

to check if the file has been included into the boot.wim file(without necessarily booting into automation), please follow the article at link below:

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

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 would be really appreciated – Thank you, Mauro


DS 7.x - Mounting boot.wim file to access folder structure (enable check/add/remove files and folders)

$
0
0
Twitter Card Style: 
summary

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 Bootwix.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 folder under C:\ , and name it for example "mount"

7 - Open a command prompt (CMD) with admin rights

8 - Run the following command (DISM) as below:  (in our example we have set folders C:\test and C:\mount - modify the command to suit your naming and locations)

DISM /Mount-Wim /WimFile:C:\test\boot.wim /Index:1 /MountDir:C:\Mount\

125.jpg

9 - Now you can access C:\Mount and browse it. - In the example below we verify Ghost32.exe has been included in the preboot configuration:

126.jpg

10 - Unmount boot.wim with the following command:

DISM /Unmount-Wim /MountDir:C:\Mount /Commit

127.jpg

If you need to inject NIC Drivers into boot.wim you may want to have a look at this other article:

https://www-secure.symantec.com/connect/blogs/ds-75-adding-nic-drivers-bootwim-winpe-40-pre-boot-configuration

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 would be really appreciated – Thank you, Mauro

DS 7.5 - Automation Tasks are in Queued or Pending state

$
0
0

Problem:

Automation Tasks are in Queued or Pending state with "Waiting for the agent to get the task" message.

19.jpg

Cause:

The PectAgent (SMA in automation) does not get registered and tasks don't get executed

Troubleshooting Steps:

1 - Run a report as follows:

reports -> all reports -> notification server management -> Agent -> Agent registration Status

2 - Search for Status: "pending" or "blocked"

20.jpg

3 - Check the "Agent Registration Policy" at:

Settings -> all settings -> Agents/Plug-ins -> Symantec Management agent -> Settings -> Registration Policies

21.png

"Agent Registration" must be "ON"

and for troubleshooting purpouses "Host Name" should be set to "*"

22.jpg

4 - Access Resource Membership update:

23.jpg

5 - Run a Policy Update Schedule:

24.jpg

6 - reboot Pectagent by launching runagent.bat in automation

70.jpg

7 - Test The task

71.jpg

72.jpg

Thank You,

Best Regards,

Mauro

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 would be really appreciated – Thank you, Mauro

NBS Question

$
0
0
I need a solution

Is it possible to password protect task in the Intial Deployment so that jobs could not be run on accident by end users?

 

If this is not possible can I put in a feature request for that as option in a release down the line.

Unable to deploy a disk image using WInPE

$
0
0
I need a solution

I am trying to deploy a disk image to a computer that I have already deployed some months ago the same image.

When starts the WinPE stored in a USB memory, the image deployment is waiting without other message.

Before start the image process, I deleted the computer description in Symantec Management Console.

Any idea how to solve this missed imaging ?

 

Thank you for any suggestion..

Netboot (OSX) name being sent to clients is always netboot001

$
0
0
I need a solution

Soooo looooong story short there are some tweaks that can be made to the rc.netboot file in the /etc folder of the netboot.dmg file in the netboot folder on the deployment server.    THrough a lot of testing I've modified the do_init() function with the following tasks to prove where the naming of the netboot image comes from. 

    # set the ComputerName based on what the NetBoot server told us it was
    machine_name=$(ipconfig netbootoption machine_name 2>&1)
    if [ $? -ne 0 ]; then
        echo "no machine name option available"> /opt/err.txt
    else
        echo "Setting ComputerName to ${machine_name}"> /opt/err.txt
        scutil --set ComputerName "${machine_name}"
    fi
    cd /opt

When I do that I always get the line Setting ComputerName to netboot001 (Now OSX will change this to "netboot001 (2)", "netboot001 (3)"... later in the process, but at this point in the boot process it's proof of the name I believe.)   Now having this improper name during boot can be problematic.  I am in the process of changing the name post boot, but ideally I would like the netboot server to hand out the correct name to begin with.   Since the communication is already there all I have to do is catch whatever it is on the deployment server that generates that name and throw a query before it pushes it down the pipe.   If anyone has any information on what pushes that down I'd love to know and will share the resulting modifications if it helps ayone.  

Thanks!  I tihnk having this will make imaging and many other tasks much more functional (Won't change the name of the computer in the manager etc...)

Symantec Deployment Solution Webcast - December 3, 2014

$
0
0
Location: 
WebEx
Time: 
Wed, 03 December, 2014 - 13:00 - 14:00 EST

Please join us for our next Symantec Endpoint Management webcast on Wednesday, December 3.

Hugo Parra, Director of Product Management, and Rob Barker, Technical Education Consultant, will be our guest speakers. The topic will be Symantec Deployment Solution powered by Altiris technology.

We invite you to submit questions on Deployment Solution in advance by posting them in the comments below.

Sign-up today!

WebEx Details:
https://symantec.webex.com/symantec/onstage/g.php?d=769249714&t=a

Event number:
769 249 714

Event password: 
sym123

-------------------------------------------------------
Teleconference information
-------------------------------------------------------
US/Canada Toll Free: 877-719-0468
Int'l Toll: 719-325-3066
Participant Passcode: 280647

Image & Updates File Location on Altiris 7.1

$
0
0
I need a solution

Hello All,

     In Altiris 7.1 how can i determine where images we have created are being stored and where Updates and Drivers are being stored?  We had an issue with a NAS device that crashed and it had a folder named Altiris.  I'm not sure it was actually ever used to store anything so I wanted to confirm where everything is pointing to.  Thanks for the help.

1415743521

ITMS 7.5 SP1 HF4 is now available

$
0
0
Twitter Card Style: 
summary

Announcing the availability of ITMS 7.5 SP1 HF4.

This release is available through SIM and contains a number of fixes for the following components:

  • Symantec Management Platform
  • Deployment Solution
  • ULM (UNIX-Linux-Mac) Agent

Release notes are available at http://www.symantec.com/docs/DOC7940

Cheers,

-Hugo

DS 7.5 - How to include ghost32.exe in a bootable USB or .ISO created with bootwiz.exe

$
0
0
Twitter Card Style: 
summary

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 bootwiz as below:

111.jpg

Locate ghost32.exe here on the SMP:

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

4 - Now you can add ghost32.exe to the newly created pre-boot configuration by adding the file or folder to the file structure in bootwiz

(Right click to create a folder and to add the file)

112.jpg

5 - Please remember to re-create the preboot configuration(create boot disk)

113.jpg

6 - Save your .iso in a folder easily accessible or onto a USB or CD/DVD and remember to select "stand-alone boot" as on picture below:

115.jpg

Ghost32.exe is now included into the boot.wim file. After booting into WinPe4.0 you will be able to access Ghost32.exe by browsing the X:\ drive in automation

to check if the file has been included into the boot.wim file(without necessarily booting into automation), please follow the article at link below:

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

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 would be really appreciated – Thank you, Mauro

DS 7.x - Mounting boot.wim file to access folder structure (enable check/add/remove files and folders)

$
0
0
Twitter Card Style: 
summary

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 folder under C:\ , and name it for example "mount"

7 - Open a command prompt (CMD) with admin rights

8 - Run the following command (DISM) as below:  (in our example we have set folders C:\test and C:\mount - modify the command to suit your naming and locations)

DISM /Mount-Wim /WimFile:C:\test\boot.wim /Index:1 /MountDir:C:\Mount\

125.jpg

9 - Now you can access C:\Mount and browse it. - In the example below we verify Ghost32.exe has been included in the preboot configuration:

126.jpg

10 - Unmount boot.wim with the following command:

DISM /Unmount-Wim /MountDir:C:\Mount /Commit

127.jpg

If you need to inject NIC Drivers into boot.wim you may want to have a look at this other article:

https://www-secure.symantec.com/connect/blogs/ds-75-adding-nic-drivers-bootwim-winpe-40-pre-boot-configuration

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 would be really appreciated – Thank you, Mauro

Receiving ‘PXE-M0F: Exiting Intel PXE ROM’ When Attempting to Capture Image

$
0
0
I need a solution

Good afternoon,

I’ve got a VM that I’ve been using to put together our “gold standard” image. I finally have things setup right and want to capture the system, but I am running into this problem with the PXE server.

I found this issue in the thread http://www.symantec.com/connect/forums/pxe-server-error-pxe-m0f-exiting-intel-pxe-rom , but it was for an older version of DS. Additionally, Thomas Baird mentioned that this is essentially a “feature” and prevents known computers from accidentally going into PXE boot, but it’s preventing me from getting into PXE at all. I have booted to PXE with the VM before, so the server recognizes it, but I don’t want to have to restart the server every time I want to re-access the server to make modifications to our image or something.

What’s the best solution to this issue? Is there a way to tell the system to respond to all computers with the same process such as the ‘press F8 to continue to PXE boot’ option?

Thanks,

Johnathan

Site Server designation in NS 7.5

$
0
0
I need a solution

Hello all,

I haven't done in this in so long...I kind of forgot!

Current setup:

NS 7.5 SP1 HF2 with NBS and Task imaging and serving 2200 clients. PXE is leveraged by IP helper at the switch.

Added a Site Server with Task and Package to take load off of the NS. Now, do I still retain Task Service on the NS or remove it and have Task completely handled by the new Site Server? Should NBS be handled by this new Site Server or let the NS continue to provide that? I see agents starting to communicate with this Site Server and some still communicate to the SMP.

Also, the SMP and Site Server are in different subnets.

1418166559

PectAgent sitting in automation

$
0
0
I need a solution

Our current imaging process on 7.5.1 HF4 works fine for 5-8 PC's. After that the subsequent machines boot into automation and the pectagent sits idle. The deployment of the .gho image never happens. The only way to fix it is to delete the resource and retry the image again until it works. Does anyone know what could be causing this or where to check? We are gathering pectagent logs now. The other weird thing is the job will be running but when you click the details for it the history is gone. I have no idea why the history just disappears for some.

Thank you.

Enabling the Bitlocker Usage within the Deployment Solution

$
0
0

Hello Everyone,

Not sure if this is possible, however if this can be considered, lots of customers are enquiring about the bitlocker support within the Deployment Solution from Imaging tools just like WDS.

So far have got to know that for the bitlocker to be working we may have to customize the WinPE for its usage. We may have to look towards it by including by some means the trusted platform module.

As of now we know that if we want to capture the Image of any operating system thats encrypted, the ghost does it via sector by sector which makes the image large. And the workaround so far is to capture the image which is not encrypted and after the deployment then encrypt it.


existing Symantec endpoint protection un-installation

$
0
0
I need a solution

Can any one help me out,

i would like to un-install SEP from all of the clients in domain (280 PC's)

is there any way to un-install SEP by using Batch file or, any tool to un-install all once

your response highly appreciate.

ITMS 7.5 SP1 HF4 is now available

$
0
0
Twitter Card Style: 
summary

Announcing the availability of ITMS 7.5 SP1 HF4.

This release is available through SIM and contains a number of fixes for the following components:

  • Symantec Management Platform
  • Deployment Solution
  • ULM (UNIX-Linux-Mac) Agent

Release notes are available at http://www.symantec.com/docs/DOC7940

Cheers,

-Hugo

Software installation at the time of Image Deployment

$
0
0
I need a solution

Hello

Can anyone help me how to install software or to do software deployment at the time of Image deployment.

While deploying image we need to deploy software package as well.

Anyone having idea about the same.

Computers which aren't reporting inventory to NS - 'N' Days

$
0
0
Twitter Card Style: 
summary

Very often user wants to know and see list of managed endpoints, which aren't reporting their basic inventory to NS Server - Last 'N' Days

  • Attached "Computers which are not reporting basic inventory _ already last 'N' days.xml" report is created on SMP 7.5 SP1 HF4 (Should for 7.5.x as well)
  • Attached "Computers which are not reporting basic inventory _ already last 'N' days (7.1 SP2 MP1.1 v10).xml" is created on 7.1 SP2 MP1.1 v10 and should work for 7.1 SP2 MP1.1 vx versions.

222InactiveComputers.jpg

How to import existing .xml report

  • Open SMP Console -> go to "Reports" -> mouse right click menu on root "Reports" folder -> click "Import" -> choose required .xml -> click "OK".

ImportReport.jpg

  • You can edit SQL Query via "Edit" mode for imported report.

image not taking up NIC Card drivers

$
0
0
I need a solution

Hello

We have installed deployment solution 6.9. We are trying to upgrade All windows xp embedded POS ready 2009 system to windows 7 professional.

We have captured one standard windows 7 image and trying to deploy image on system on which windiws xp embedded POS Ready 2009 operating system installed. Here image gets deploying on the system but it stuck for NIC drivers.

We have check the necessary drivers are present in drivers DB but still it stuck on the NIC card drivers installation.

Need suggestions for the same or how I upload drivers properly into Driver DB.

0
Viewing all 645 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>