Endpoint Management Community Blog

Unable to map a network drive with a Windows PE boot disk

Randall Newnham | 26 Oct 2009 | 4 comments

This is either due to a lack of network drivers, or due to the drive mapping command, net use, executing too early in the boot sequence.

First, you must verify that you have networking capabilities in the boot environment. To do this, boot with your existing Windows PE boot disk , then choose Quit to exit Ghost. At the command prompt, type the following, then click Enter:

ipconfig/all

If an IP address is present, and is not 169.xxx.xxx.xxx, then you have networking capabilities. If this is not the case, you will need to add the appropriate network driver according to these instructions:

How to add drivers to DeployAnywhere or WinPE.

http://service1.symantec.com/support/on-technology.nsf/docid/2008050916132860

If you have networking capabilities but still cannot map a drive, it is likely that the net...

Problem with ghost imaging

4G | 15 Oct 2009 | 4 comments

I am experiencing this problem during imaging on our computer. Any solution?

Date   : Thu Oct 15 12:12:28 2009
Error Number: (29004)
Message: Read sector failure, result = 1, drive = 128, sectors 44919505 to 44919569
Version: 7.00 (Mar 22 2001, Build=245)
License: XQ199905
Command line arguments:
Active Switches :
       Spanning
ProgMode            : PROG_LOCAL
PathName            : \GHOSTERR.TXT
DumpFile            : G:\712N049.GHO
DumpPos             : 1157874587
FlagImplode         : 2
FlagExplode         : 0

Mouse IRQ Status : Not...

Deploying Ghost Console and Imaging Server

Steven Grove | 29 Dec 2009 | 2 comments

I have just started a new job in a new place with new people. We have a 16 blade HP server to migrate all services to in the neat future. As of now, multiple services are running on the same servers with no (nada, zip, zero) redundancy. They know it, and they have been trying to get it up but DIACAP has taken all their time. I will chronicle my trials and tribulations on my journey to migrate the Console services and images to a new blade.

Official release of Deployment Solution 6.9 sp3

Marcello D'Angelone | 25 Aug 2009 | 5 comments

The official release of Deployment Solution 6.9 sp3 has now been released.

The product is available to download from:

http://www.altiris.com/Altiris/Download.aspx

Release Notes:

https://kb.altiris.com/article.asp?article=47793&p=2

Cheers

Altiris Beta Program: Deployment Solution 6.9 SP3 Beta - Now Available

adtlink | 23 Jun 2009 | 1 comment

We are pleased to announce the release of Deployment Server 6.9 SP3 into the beta cycle. We anticipate the beta cycle to last approximately 5 weeks.

Outlined below are some of the new features for this release:

DAgent

Use customdata.ini – The user has the ability to have DAgent report only those NICS which they want. It will filter the NICS depending upon its description and MAC Address.
Right-click uninstall - In the Console when user right-clicks on the computer, under Advanced tab and clicks on the “uninstall agent” Dagent will be uninstalled from the client computer. This facility is only provided from the console side.

New OS Support

Windows Vista SP2 (x86, x64)
Windows 2008 Server SP2 (x86, x64, ia64)
Windows 7 (x86, x64)
Windows 2008 Server R2 (x64, ia64)
VMWare 4.0

We now ship GhostWalker which is part...

How to fix the boot error when restoring a non-syspreped Windows 7 image.

Screenbert | 23 Jun 2009 | 1 comment

When working with our core image for Windows 7 I found that restoring an image that has not been syspreped results in a boot error. You can go through the windows repair and let it try to "fix" the issue. Or you can simply use bcdedit to "reset" to boot information. I never had this problem with Windows Vista Images, so it seems to be the new boot manager with Windows 7 that cause this issue. It's probably a good thing to keep unauthorized (and un-sysprepped) images off of your network.

1   ) Restore the Windows 7 image onto the computer
2   ) Boot with the latest version of your Altiris bootdisk.
3   ) Run these commands:
3a ) bcdedit /set {default} device partition=c:
3b ) bcdedit /set {default} osdevice partition=c:
3c ) bcdedit /set {bootmgr} device partition=c:

Ghost Solution Suite 2.5 Console task fails with error referring to SATA Controller.

Randall Newnham | 08 Jun 2009 | 0 comments

Some machines using Intel's ICH9 and ICH10 SATA Controllers, such as Dell Optiplex 755 and 760 machines, have been seen to not work with the storage controller drivers in the Ghost database. The error encountered is typically "To virtual partition: failed. Drivers could not be found in the PreOS for the following devices...", and it names the Intel SATA controller. Importing this driver into Ghost should prevent these errors. Here is the link to the download at Intel's site:

http://downloadcenter.intel.com/Detail_Desc.aspx?a... Vista*&lang=eng

Once that is downloaded, the file will meed to be extracted from the self-installing archive. To do this, copy it to the root of...

Question in Regards to Ghost Solution Suite

JasonD | 02 Jun 2009 | 4 comments

hey everyone,

I recently asked this question in another forum but received some rather unfavorable answers so I thought that I would try posting it to the community here and see what everyone had to say. I currently have GSS 2.5 installed on a win2003R2 server and I have some how managed to mess up my PE file. To fix it I would like to completely remove GSS and start fresh, please feel free to suggest an alternative.

Anyways, I have run the uninstaller from CD and and deleted the symantec files from within the Common Files within Program Files. However, I am still finding my old modified PE when I look at the Boot Wizard after re-installation of GSS. So, how can I COMPLETELY remove GSS 2.5 and all of the modified files?

p.s. I apologize if this is the wrong place for this question, just looking for an answer and this seemed appropriate. Thanks for any help you can provide.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- Jason
SysAdmin /...

Ghost Error: "Incompatible clone switch on the server side"

Randall Newnham | 12 May 2009 | 0 comments

Error: "Incompatible clone switch on the server side" occurs when using the -sure switch in the boot media to automate an image deployment or capture.

This error occurs when using boot media to automate joining a Ghostcast Server session when neither the boot media nor the Ghostcast Server have the disk number specified. To resolve this, either add the -clone switch to the boot media, or specify the Disk number (and Partition number, if a partition operation is desired) to the Ghostcast Server in the "Client command line options" area.

Can not finish a Full Managed Backup with Ghost 14 without Error EBAB03F1

bruce_in_ma | 03 May 2009 | 2 comments

Problem: Can not finish a Full Managed Backup with Ghost 14

After running a Full Managed Backup.
I get following error on Norton Ghost 14.0. 4.30.30167:

Error EC8F17B7: Cannot create recovery points for job: Drive Backup of (C:\) MASTER2007. Error E7D1001F: Unable to write to file. Error EBAB03F1: The process cannot access the file because another process has locked a portion of the file.
Details: 0xE7D1001F
Source: Norton Ghost

This error is consistent when writing to the external USB Rosewill R2-JBOD USB 2.0 DUAL-BAY 1.5GB box.

I get this error only when I send the file to a 1.5TB Seagate ST315003 41AS USB devise.
Another USB devise 250GB Seagate ST325082 4A USB devise does not have this problem.

I read everything you had online about this problem, but nothing helped or explained the problem. Actually I believe wrote that Symantec could not reproduce the problem.

So therefore I will attempt to...

Endpoint Management Community Blog

Links

About Endpoint Management Community Blog

Filter by:

Blog Tags