Hello.
I'm updating my win 10 to last version 1703 and before to install this update it shows error because Dell storage manager driver (Microsoft article base 941024) must be uninstalled. It seems to be something related to altiris services. Any one know how to solve this?
Thanks.
In the console, you can right click on an object and tell it to install the Automation Folder. I will receive status updates that it is copying down, but it always fails for me on "Executing File". I THINK this is my over-zealous virus scanner killing it (I say think, because it DOES kill it if i run the installer manually)
Where does the console copy its temporary file on the client system so it can run? I want to whitelist that for my AV
thanks!
I am trying to create a boot disk using gss 3.1,but I keep getting an error saying the file does not exist c:\program files (x86)\altiris\express\deployment server\bootwiz\platforms\winpe 4\x86\templates\startnet.cmd. I have tried reinstalling the ADKs. I've tried usings WinPE 4.0, 5.x, and 10.0. I get the same message everytime after getting to 80% of Copying files to the production area. I was able to create a bootable usb when we first implemented GSS3.1 but now even those configurations will not allow me to create a boot disk. My bootable usb still works, so I can still create and deploy images, but I need to be able to create a disk for an older pc that is not able to boot from USB.
Hi,
I have a little problem with new Ghost solution suite 3.2 with a image create task. I have a basic situation:
When I do it in the old way, everything is fine - sysprep do his job and computer start. But when I do it in the standard way, I get error 0xc000000f - bluescreen - system cannot access to \Windows\system32\config\system... registry.
When I restore image in the standard way, everything is normal.
I have done some research and something is wrong when PC boot to PXE WinPE environment and create image. I have done about 50 tests and everytime it goes wrong, when I create image in standard way -with image create task - boot to PXE or Automation folder.
I thing, the WinPE task do something with BCD :(. But, when I am in audit mode, create image with create image task and restart, PC start back to audit mode normaly. But when I start sysprep, PC not boot and go into bluescreen 0xc000000f :(.
Any idea? :)
Thank you.
Jan Cernohorsky (John)
After starting with a Ghost multicast deployment job to 17 workstations, it was averaging 600 Mb/min for the first hour or so of the task. Then all of the sudden, it comes to complete crawl. You can watch the MB tansmitted go from 20-30 MB each second to 1 MB every few seconds. It will finnally slowdown to about 40 MB/min for the overall mulitcast job and take 36 to 48 hours to complete. What is very intreseting is that I can run another 15 workstations connected to the same server unicast and they all finish up in about 2 hours. Also, when I log into the server to check to files it is accessing and the overall progress, I am not seeing it accessing any of the *.gho or *.ghs files like it once was. Is there something wrong with ghostsrv.exe and how it access files?
Hi all.
Currentyly im using ghost 8 to backup and restore images on an old dell PC. i was given the boot cd by a collegue and it works great.
I have just been given a HP elite book G2 to image and have found that the keyboard and mouse is unresposisive when ghost loads up. I have read around that its because the version of ghost im using does not support USB 3.0 that is on the HP PC.
I have downloaded the trial version of GSS 3.2 with the intention of trying to create the same boot disk as the one i had on ghost 8 but it is not giving me the option to backup and restore when i boot from the cd.
any help would be much appretiated
Whe I deploy an image to a PC, the OS is being renamed. How do I prevent that?
Example:
I have 1 PC, that PC has 3 images that is can use (W7, W8, WX). All 3 images were created and dumped seperately and the HOSTNAME for each is unique. If I perform a reimage, the process changes the HOSTNAME after the imaging to be whatever is specified in the "computer object" in the Ghost Console. I don't want that, I want Windows 8 named W8, Windows 7 names W7, and Windows 10 names WX.
Please advise on how to prevent this additional configuration.
New to Ghost (used it many year ago !)
Just downloaded trial. All I want to do is to image an HP tablet fresh out the box before blatting the HP recovery partition to test with SCCM
At the end of testing use USB stick to restore original system as was
So Ghost and the image need to be on the USB stick
Hopefully a straightforward question - if you just point me to correct docs thank you
Is there any way in GSS3.2 to use CLI? I want to create a new computer with MAC and computername, import it in GSS and start an image deployment. Is any of these steps posible, or on the roadmap?
Hi,
I'm having a strange issue that sounds like a permissions but I just can't trace it.
I'm using GSS3.2 (Build 1243) and tring to pull an image from a PC.
The PC boots from the automation folder fine.
Maps drives correctly to the main ghost server.
Starts pulling the image from the workstation.
The problem happens when ghost tries to create the first split file. it generates the error on the client.
"Cannot create image file I:\$recycle.bin"
Win32 error (0x00000005)
Message description: Access is denied.
(662)
On the server, the first section of the image file is there in the proper location and created. "I:\images\test.gho" The account has full access rights to that location.
On the workstation when the error appeared I open a command prompt and was able to copy/delete/rename files in the I:\$recycle.bin folder.
Tested on a second system - same result.
Reduced the split file size to 200Megs - same result.
included the -FRO option - same result.
Any and all help for finding a solution would be greatly appreciated.
Thanks,
Ed
https://support.symantec.com/en_US/article.DOC10478.html
Symantec is adding incremental value into Ghost Solution Suite 3.2 maintenance releases by including new features and product updates.
To indicate this change, the Hotfixes are renamed to Release Updates (RU). The first releases that will use the new title will be the Symantec™ Ghost Solution Suite 3.2 RU1.
The upgrade experience remains the same as for the Hotfix releases in the past.
The cadence of these releases will remain the same: approximately every 8 weeks.
I'm using GSS 3.1 MP5. When using peer-to-peer Multicast for "distribute disk image" task the Windows 10 sysprepped image deploys and boots up normally.
I switched to using GhostCast Server for the "distribute disk image" task and now the image lays down normally but won't boot to production. I get a black screen with ">>checking media presence...... >>media present..... >>Start PXE over IPv6." Nothing else changed.
When checking the BIOS boot sequence, there is no "Windows boot manager" option.
So, then in the "distribute disk image" task I unchecked "Automatically perform configuration task after completing this imaging task". Same problem.
Can you help resolve this problem?
Thanks,
Shauna
https://support.symantec.com/en_US/article.DOC10478.html
Symantec is adding incremental value into Ghost Solution Suite 3.2 maintenance releases by including new features and product updates.
To indicate this change, the Hotfixes are renamed to Release Updates (RU). The first releases that will use the new title will be the Symantec™ Ghost Solution Suite 3.2 RU1.
The upgrade experience remains the same as for the Hotfix releases in the past.
The cadence of these releases will remain the same: approximately every 8 weeks.
Currently, we are able to boot to physical media (MBR and GPT) on both WinPE4 and WinPE10 onto Dell and Lenovo hardware and deploy Windows 10 x64 Enterprise (GPT format for UEFI boot) via Ghost 12. Recently we received a few models with NVMe type disks and since the machines no longer boot to Windows desktop environment after the image drops. After the image drops and reboots, we are stuck at the boot selection screen. Selecting the hard drive does not boot to Windows but rather it just flashes the screen quickly and remains at the boot device selection screen. This process has worked for over a year but suddenly breaks with the new hardware.
Any ideas what could be causing this?
Hello,
For years we have happily used DS6.9, now re-branded to Ghost Solution.Until now we deployed a single image captured on MBR partition and deployed for pcs running in BIOS legacy mode.
Windows 10 offers new security features that works only in UEFI mode. It has become a business requirement now. I started looking into it. The first issue I come across is that PC does not boot into PXE if I disable BIOS legacy mode and enable UEFI only.
I do not receive any errors, the PXE agent screen just disappears after few seconds and goes back to the start menu. I use the HP 640 G2 model. On the same PC, Pxe agent boots fine in the legacy mode.
On GSS console I added WinPe 10 64 bit image.
Any ideas ?
Thanks
Tomasz
Hi Everyone,
I just wanted to know does Ghost Solution suite ver 3.2 include Multicast Server and Ghost program.
thanks,
Hi,
I'm having an issues trying to install an automation folder on a Windows 10 system.
I get the message "No appropriate bootworks NIC found. Use boot Disk Creator to Create a Bootworks install package."
The same system with windows 7 works fine. It detects the NIC properly.
Server: GSS Ver 3.2 (Build 1325) R1.
Anyone run into the same problem?
Ed
I have a large scale network where we image lab PC's (win7) over the network. If I reimage 3 PC's using unicast average time is 30 to 45min to reimage. If I bump that up to 5 or more PC's to reimage the reimage process jumps to 4 to 5 hours. I'm using a WinPE boot disk where it launches Ghost with no switches. Is there a limitation on how many devices I can reimage at one time? The images are on average 20gb in size. Network is a gig network. Images are stored on a network VM server.
thanks
Winston
My new "Distribute Disk Image" jobs were failing, however the old images was working fine. No error in ghost, but after aclient started in winpe, it just ran for a few secs, and restarted the computer. After a lot of work I found out that the job had "> /dev/console" in the Additional Parameters. Removing it seems to solve the problem, but what is going on here? It doesn't show the gui when applying the image, but atleast it's working now.
We are attempting to image a new Dell Precision 7710 Laptop with a 256G M.2 PCIe SSD. WinPE loads and ghost32.exe launches but after selecting the image, the SSD shows as grayed out and we cannot image the drive.
If, however, we select Disk-to-Image, the drive is available for selection.
We have updated the system BIOS on the laptop and tried every BIOS configuration in Legacy and UEFI that we can find. We are still unable to image these new systems. Is there something we are missing?
The environment is Deployment Server 6.9 with Ghost 12.x, WinPE 4.0. I have tried Ghost32.exe 12.0.0.4570 and 12.0.0.10514. (We are getting ready to move to GSS 3.2 but not there yet.