Hi, I'm having a problem with my symantec Ghost64.exe to launch in WinPE, i have been only ghosting 2nd,3rd and 4th gen PCs now we have 5th 6th 7th and 8th Gen PCs which i thing i need an update for those because it doesn't install the network driver with those, can you please help me find the updates for the higher end CPUs.
regards.
The DAgent Service doesn't not retain the manually entered GSS console address when you got into DAgent configuration and alway swithces to multicast. What setting or file do I need to clear on the system so the address will stick?
James Trice
Hi, I'm having a problem with my symantec Ghost64.exe to launch in WinPE, i have been only ghosting 2nd,3rd and 4th gen PCs now we have 5th 6th 7th and 8th Gen PCs which i thing i need an update for those because it doesn't install the network driver with those, can you please help me find the updates for the higher end CPUs.
regards.
So I was on Ghost Solution Suite 3.2 and was having an issue with a new model of Dell Latitude 5300 client Laptop only showing a black screen after loading from the PXE server. Right before it goes to a black screen I see the windows 10 logo then I get no display the ghost session does connect and it will create or image luckily so It still functions. I am not sure what would cause the black screen though on the load of the PE.
I have also updated to GSS 3.3 to test if there was some kind of fix for this issue but it still is happening. Has anyone had this black screen issue on any laptops or computers before?
Not sure what is causing this because it is only specific to this model. Could it be the Video driver not loading in windows PE or is it.
Also to note I tried an external display same issue.
Hi
I'm using 3.3 RU2 on server 2012r2, i downloaded RU3 and go through the install.(simple) .. it fails at copying files with application terminated? Any ideas why?
Is there any way to confirm that Symantec will continue to support Ghost Solution Suite as I see almost no activity on it.
What is the cost structure and how do you buy it. I've contacted 3 resellers with no response and am very confused over the pricing.
Thanks,
Server is GSS 3.2 RU3.
Using USB Boot method.
Our current image is designed to use Windows Boot Manager in UEFI mode only.
Only affects the following systems:
1) PC/Laptop was running Windows 10 but bios was in legacy boot. Change BIOS to UEFI before imaging.
2) PC/Laptop running Windows 7 previously, regardless of UEFI or Legacy boot method in BIOS.
The first time the job is pushed in either of the above situations the device will BSOD during OOBE.
Push the image a second time, but only AFTER the BSOD, it will take everythnig just fine and continue with OOBE and all other automated tasks after image.
If we try to push before allowing the machine to BSOD, it will still BSOD. Almost as if it has determined it must first fail before it will ever succeed.
Prior to RU3 we did not have this issue (everytime).
I am trying to install and run Ghost Solution Suite 3.3 RU3 on a Windows Server 2012 R2 operating system.
The image of my OS already has 2005 SQL Express. It is my understanding that this version of ghost requires SQL 2014 Express. I install SQL 2014 Express after uninstalling 2005 and then I install GSS console. I am able to install everything with no errors. However when I go to open the GSS Console using the desktop icon i continuosly receive the same error message
"Unable to connect to the Symantec Ghost Solution Suite Server DB Management Service. Please ensure this service is started and running currently."
This service does not exist however there is a service called Altiris Deployment DB Management.
I have looked into this issue on multiple sites and basically have tried everything suggested but ultimately get the same error message everytime. Is there something I am doing wrong in the installation? IS it a problem with SQL?
The worst part is I had this working at one point but then went to recreate the process and I cannot get passed this point.
Hi,
What will happen if I used up all my license in GSS and install it on a new machine ? What will happen to the new machine ? Will it recieve the Job from the console?
Also is it possible to buy 50 license and used it for 200 endpoints for imaging only? Removing the agent to the machine after a successfully image?
Thanks
I am working on and older PC with Ghost 2003. I know, but it's an old computer. In the Ghost program in Windows, I selected what I wanted to image. The computer then rebooted into PC DOS but never fully launched Ghost. Now the computer will NOT boot back to Windows. 2 questions - How do I get it to boot back to Windows (and selcting "Skip Ghost DOS and boot into Windows doean't work) and 2nd question, I have previously Ghosted boot drive I can use but I am scared it will try to boot to PC DOS as well. Is the "Boot to DOS" iset in the BIOS or something on the drive? Can I use the other boot disk without a problem?
Thank you all so much. This is a ral important computer and I need to get it running again as soon as I can.
I'm installing 3.x GSS and when i get to the SQL portion it seems my local server as having SQL, pre-pops the name/port and DB name, but when i hit next and specify either to use Windows or SQL it will fail stating its unable to login to the server using either creds. Its Server 2019 and SQL Express 2017, so curious if anyone has seen this or knows of a workaround. TLS 1 and up is still enabled, Remote connections are enabled. Inputing localhost doesnt work. All the components areon the same server.
When trying to upgrade from GSS 3.3 to GSS 3.3 RU 3, I kept getting this error when selecting the iPXE configure option - It stops at 50% with error message "Failed to install iPXE Addon for PXE Server"
From what I can tell, it was a problem in the past and it appears to be a problem again:
https://support.symantec.com/us/en/article.TECH252404.html
This is even after going over the system requirements for iPXE and had everything installed and configured (Dot.Net 4.5 Framework, IIS, all the Microsoft goodies):
https://support.symantec.com/us/en/article.DOC10918.html
So, I went through and manually installed each one of the MSI installers based on what this article had stated:
https://support.symantec.com/us/en/article.TECH253661.html
And then went back and re-configured the authentication methods in IIS manager based on what this article had stated as well:
https://support.symantec.com/us/en/article.TECH251580.html
TA-DA! iPXE is now working!
Quite a pain to get it all working, but it lives....
Has this been everybody else's experience trying to get this all to work as well?
If you get an error 161 trying to open the console here is the solution:
Open regedit
Go to hkey current user
Go to software
Delete the Altiris Key, the whole thing.
Reopen console and it sets your preferences back to as if you just installed it for the first time.
Had 3 users with broken ghost consoles and it fixed all 3.
Hi All,
I have a very wired issue with one of my windows 2008 r2 server ( which was working previously ) , i have configured Altiris Dagent service to log on as 'LOCAL SYSTEM' then none of the job is executing ,job just running forever without any sucess or failure ,when i use my domain account which have admin privilege on the system job executing as normal.I have granted permission to LOCAL SYSTEM to 'log on as a service' in security policy and also SYSTEM is not part of the 'deny log on as service' .Any idea what might be causing this issue .
Thanks In advance.
Sajeesh
I am working on creating a Ghost image of Windows 10. I am using stand alone version of norton ghost 3.3 which is the latest one from norton. Along with WINPE10. My PC is configured to boot in UEFI only mode.. I am creating image in following way: in winpe mode -->disk --> to image --> source is O.S drive --> destination --> Usb --> create Image restoration is done in following way --> winpe mode --> disk --> from image --> src=usb --> DST=drive 1. Image gets restored successfully. When I boot the target machine I get a blue screen error saying "your PC needs to be repaired". I am not sure what is wrong in this procedure. Also both the source and target machine are identical machine.. I am stuck at this phase. Could someone please help me to resolve this..
Anyone had luck using standalone ghost instances with a USB boot stick on Dell Latitude 7400? My WinPE instance hangs up and freezes when trying to load. I don't even get as far as launching ghost. Just see a Windows logo, a loading circle at the bottom, then a flash and the machine freezes.
At first I was getting just a black screen so I loaded the graphics drivers for this model into my boot ISO. Now it shows display but freezes. Have I put too many drivers in and am just burning up all the ram before I get to the ghost app?
I am working on creating a Ghost image of Windows 10. I am using stand alone version of norton ghost 3.3 which is the latest one from norton. Along with WINPE10. My PC is configured to boot in UEFI only mode.. I am creating image in following way: in winpe mode -->disk --> to image --> source is O.S drive --> destination --> Usb --> create Image restoration is done in following way --> winpe mode --> disk --> from image --> src=usb --> DST=drive 1. Image gets restored successfully. When I boot the target machine I get a blue screen error saying "your PC needs to be repaired". I am not sure what is wrong in this procedure. Also both the source and target machine are identical machine.. I am stuck at this phase. Could someone please help me to resolve this..
I am working on creating a ghost image for my machine. below are the technical details:
O.S = WIndows 10
Ghost version = 3.3 (Stand alone). This is the latest one.
Bios = american megatrends
Boot is set to = UEFI only
WinPE 10 is used along with norton ghost.
Note: I am using the default configuration of norton ghost.
Procedure i have followed to create ghost image:
Boot in WinPE Mode --> Disk --> to image --> select Src as my O.S Drive --> Select destinationa as my USB --> create.
Procedure i have followed to restore ghost image:
Boot in WinPE Mode --> Disk --> from image --> select Src as my USB Drive --> Select destinationa as my Drive 1 (My PC Hard Disk)--> restore.
Restoreion will be successfull. when i boot the machine after image restore, I get a blue screen error saying "your PC needs to be repaired"
To further test this i did both creation of ghost image and restoration of ghost on the same machine. Even then i get the same error.
Not sure what wrong i am doing. Could some one plaese help me with this.
Hello all,
I am looking for opinons and best practices where it relates to capturing an image. When I do so I rely heavily on the instructions in this article https://support.symantec.com/us/en/article.tech249488.html for disabling apps and prepping my capture machine. However this article is back from 1703/9
Is there anything that has changed?
Are there any other best practices for 1903 and 1909?
All of my GSS knowledge is selftaught, as may be a lot of people, but I fear there is something I am missing with my capture and deployment.
Thanks,
Tom
Hi,
Wondering if anybody else has come across this
We recently upgrade to Ghost 3.3 RU2 with iPXE (faster way of connecting devices to imaging sessions)
Laptops and PCs with dedicated Ethernet ports are working (when secure boot is disabled)
We have some new devices that have no Ethernet ports - we have a mixture of USB Ethernet adapters
The drivers have been added and if you use PXE they work and image fine
However if we try using iPXE they boot and download the wim file but then freeze and dont load the WinPE - we have tried leaving it all afternoon but nothing happens
If we try it again and wait until the ipxe starts and the wim file download reaches 100% and then remove the USB Ethernet adapter for a few seconds then plug it back in the WinPE session loads and the device joins the session and images fine. Its as if it gets stuck trying to pass some type of security check - maybe UEFI related.
Just wondering if anybody else has come across this issue ?
Thanks
