I need a solution
We recently changed to Dell computers and the only option is UEFI. After converting our images to gpt, everytime I hover over the file it crashes the ghost console.
0
↧
Console crashes when I highlight a gpt image
↧
No PXE-Boot when assigning job, otherwise PXE works
I do not need a solution (just sharing information)
Dear,
PXE is set up and works in my opinion.
On all clients, PXE-Boot is set as the first boot method, each client first queries the PXE server at boot time and then executes the PXE-Boot according to my settings: For clients known in the console, the PXE-Boot-Menu waits 5 seconds, then the boot from the local HDD with the locally installed operating system takes place. Clients not known in the console wait 10 seconds in the PXE boot menu and then start the Automation Agent via PXE.
If I assign an image deployment-job to a client known in the console, this client will restart as it should be. Then it should boot the Automation Agent via PXE so that the new image can be transferred to the hard disk. However, this is not the case. Instead, the PXE boot menu is displayed for max. 1 second, but it is exited immediately and the local operating system is booted from the local hard disk. The deployment-job is then shown as failed at the end.
What is the reason / What should I do?
Thanks in advance!
0
↧
↧
Ghost error during restoring
I need a solution
Good morning, Inside the company i work for we got many cnc siemens machines with a pc windows 7 and the ghost suite integrated. After a blackuot i made a backup of the 2 partitions contained inside the ssd and after that i tried to restore an old partition backup. Here i made an error, i pressed restore entire hdd and i choose the partition file. After 2 seconds i got an error from the ghost console. Now, i got the hdd without anything inside. I think the procedure canceled some configuration files but no real files. Windows does not start and during the boot up i only got a black screen. Do you know any way to try to recover the hdd?
0
↧
Ghost64.exe with WinPE
I need a solution
Good afternoon.
I'm running Ghost64.exe (12.0.0.10644) with WinPE (1903).
The screen is so little that I can't do anything.
Can anyone help me with this problem ?
Thank you
0
↧
Dell Latitude 7400
I need a solution
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?
0
↧
↧
Ghost multicast Server to client negotiation
I need a solution
Hi,
we are using ghost server to multi clients using multicast.
Just a question on bandwidth and communication.
When the image is being transferred my understanding is that the communication is via udp.
Does anyone know how the client server communication for setup works?
Also what determines the max transfer speed? I know this is the slowest client but how does this
client communicate the speed it is happy with to the server, is this again tcp?
Is there a tcp "management" stream between client and server checking for variations in speed capabilities?
Any help or if anyone knows where to find it much appreciated.
0
↧
Unable to boot to Windows automation - Status Code 116
I need a solution
Hello.
The following issue has been reported before. However, a solution has not been posted. In my case I am running on GSS 3.3, WS 2012 R2
(See https://www.symantec.com/connect/forums/unable-boot-windows-automation-status-code-116)
Our modest guess is the issueis being cause by the Altiris PXE server rather than a boot problem. But at a loss trying to solve it.
When a new image job is deployed from the server, the target PC restarts once, loads Windows and then restarts again. (The Status Detail on GSS will show "Unable to boot to automation: 116")
The BIOS options are configured correctly: Legacy/ Network = First.
If told to boot from the network, then the PC engages as it should and the job starts. But the inconvenience is, a MANUAL INTERACION IS NEEDED for the job to kick in.
Any ideas are dearly welcome and appreciated. Thanks.
0
↧
Automation boot fails with Boot Disk creator
I need a solution
Using Ghost Solution 3.3 and just updated my preboot environment. At first, the machine complained about the NIC drivers with "Restarting DHCP clilent service" when booting from the automation folder. I updated them, reinstalled the automation folder and was able to complete my task.
However, when I created a bootable USB with the automation folder from the same environment, I got the the "Restarting DHCP clilent service." Again, it's the same environment, yet I get an error when creating a USB. I've created the bootable USB by using the boot disk creator and trying an ISO. Thoughts?
Because I was able to boot into it and deploy images, I know it works. I'm jsut not sure why the USB isn't working.
0
↧
iPXE and Secure Boot
I need a solution
So I managed to implement iPXE on our Ghost server that is running 3.3 RU2.
It can boot into the PE environment in under 30 seconds! However, that is only with Secure Boot disabled. When Secure Boot is enabled you get a BSOD type screen.
I see the issue is already logged under this Tech article, https://support.symantec.com/en_US/article.TECH252464.html
It says the cause is unknown, but it is because of secure boot. It makes sense the Secure Boot doesn't allow it, but is there any known fix or can there even be a fix without disabling secure boot?
0
↧
↧
ReJoin Domain After Scripted Install
I need a solution
Hello
I am doing some testing with doing scripted installs for Windows instead of doing a sysprepd image.
Currently the biggest issue I'm having is that I cannot get the computers to rejoin the domain. I've tried doing the personality capture, but it only renames them, doesn't join them to the domain.
0
↧
iPXE and Secure Boot
I need a solution
So I managed to implement iPXE on our Ghost server that is running 3.3 RU2.
It can boot into the PE environment in under 30 seconds! However, that is only with Secure Boot disabled. When Secure Boot is enabled you get a BSOD type screen.
I see the issue is already logged under this Tech article, https://support.symantec.com/en_US/article.TECH252464.html
It says the cause is unknown, but it is because of secure boot. It makes sense the Secure Boot doesn't allow it, but is there any known fix or can there even be a fix without disabling secure boot?
0
↧
ReJoin Domain After Scripted Install
I need a solution
Hello
I am doing some testing with doing scripted installs for Windows instead of doing a sysprepd image.
Currently the biggest issue I'm having is that I cannot get the computers to rejoin the domain. I've tried doing the personality capture, but it only renames them, doesn't join them to the domain.
0
↧
Post Distribution Services Are Disabled
I need a solution
Very similar to an issue discussed here but I didn't want to ressurect a dead thread.
After distributing an image to a HP Z6 G4 workstation the machine will not complete its configuration. When I visit the machine and login using a local administrator account I find that the "DHCP Client (dhcp)" and "TCP/IP NetBIOS Helper (lmhosts)" services are set to disabled. If I configure both services to "Automatic", restart, and then have Ghost perform a domain join everything appears normal.
The first time this happened I thought it was a misconfiguration issue from trying to capture and distribute an already established/dirty image. The second, and most recent, time I created an entirely new build from scratch but experienced the same results.
Similar to the linked thread the machine in question has two NICs. The first is listed as a Intel(R) Ethernet Connection (3) I219-LM and is disconnected and not in use. The second is a Intel(R) Ethernet Connection X722 for 1GbE.
Also similarly the image was created without using Sysprep against a Windows 10 Build 1903 system.
0
↧
↧
Unable to Image HP Stream
I need a solution
Hi Everyone,
I have several HP Stream 11 Pro G2s that I am attempting to image. These laptops have no networking ports so the only way I can do this is by using a Ghost Boot Disk created with Standard Tools and send the image to a local USB drive. The laptops are Windows 10 with GPT partitioning for UEFI booting. Currently the boot disk is booting with MBR (I'm unable to make the boot disk boot via UEFI).
The problem is occuring when I go to create the image. The Ghost Boot Disk boots perfectly, and starts Ghost (I'm using the x64 version). I can select the onboard eMMC drive and I can select the USB drive I want to send the image too; however, as soon as I start I'm immediately presented with a Usage Error 662. I've googled the error and tried different drives, I've tried swapping which ports the boot drive and the data drive are in. I even attempted to send to send the image to the Ghost Boot Disk drive, no effect. Same message. Everytime.
The only time I can get the message to change is if I attempt to send the image to a folder within the data drive. Then Ghost generates an Internal Error 8027 message.
I'm at a complete loss here. I know that I've successfully imaged these computers before (past me, unfortunately, did not write down the instructions), but now they refuse to work no matter what.
Any help would be supremely appreciated.
Thank you!!
0
↧
PXE don't start
I need a solution
Hi all,
I have all tutorials and all videos read and watch but I don't have a solution for my problem. I have no idea what to do in my case.
I have GSS Suite on a Server 2012R2 in a VM ESXI and on the same VM machina a windows 7 prof. Client. If I want to boot PXE
I become the following screen and after this my Win7 boot normaly but don't boot PXE. Is there anyone who have the same problem?
Thanks for your help
0
↧
Unable to Image HP Stream
I need a solution
Hi Everyone,
I have several HP Stream 11 Pro G2s that I am attempting to image. These laptops have no networking ports so the only way I can do this is by using a Ghost Boot Disk created with Standard Tools and send the image to a local USB drive. The laptops are Windows 10 with GPT partitioning for UEFI booting. Currently the boot disk is booting with MBR (I'm unable to make the boot disk boot via UEFI).
The problem is occuring when I go to create the image. The Ghost Boot Disk boots perfectly, and starts Ghost (I'm using the x64 version). I can select the onboard eMMC drive and I can select the USB drive I want to send the image too; however, as soon as I start I'm immediately presented with a Usage Error 662. I've googled the error and tried different drives, I've tried swapping which ports the boot drive and the data drive are in. I even attempted to send to send the image to the Ghost Boot Disk drive, no effect. Same message. Everytime.
The only time I can get the message to change is if I attempt to send the image to a folder within the data drive. Then Ghost generates an Internal Error 8027 message.
I'm at a complete loss here. I know that I've successfully imaged these computers before (past me, unfortunately, did not write down the instructions), but now they refuse to work no matter what.
Any help would be supremely appreciated.
Thank you!!
0
↧
Bluescreens after image deployment
I need a solution
I've been struggling with this issue (as my post history shows) for a long time. Now it's time to create a new image and I'm running in to the same sort of issue. When I sysprep a machine to capture the image, everything goes fine. After it captures, the machine boots into OOBE. No issue there. However, if I deploy the captured sysprepped image with GSS, after the image is laid down, the machine boots to a blue screen with a registry error 0xc000000f . When I boot into the machine from a USB drive and open a command prompt, I run notepad and see that GSS is writing the unattend file and aclient.cfg to the system reserved partition.
Here's what I see in a cmd window after the image is deployed:
M:\>M:\Ghost\ghost64.exe -CLONE,MODE=RESTORE,SRC="Z:\Sysprep\W10NEW\W10SYSPREP.gho",DST=1 -sure
M:\>RDeploy\Windows\x64\firm.exe copy ".\Temp\d5002194.cfg""d1p*:\aclient.cfg"
Copy .\Temp\d5002194.cfg d1p1:\aclient.cfg
\aclient.cfg copied successfully
Copy .\Temp\d5002194.cfg d1p2:\aclient.cfg
\aclient.cfg copied successfully
M:\>if "0" == "0" GOTO :EOFCfg
M:\>RDeploy\Windows\x64\firm.exe copy .\temp\5002194.xml d1p*:\windows\panther\unattend.xml
Copy .\temp\5002194.xml d1p1:\windows\panther\unattend.xml
\windows\panther\unattend.xml copied successfully
Copy .\temp\5002194.xml d1p2:\windows\panther\unattend.xml
\ - This is where it cuts off and the machine reboots but I assume it says it was copied successfullyfirm.exe is copying the aclient.cfg and the unattend.xml to 2 partitions - I'm not 100% sure that this is what is causing the blue screen, but how do I make it stop doing that and make it just copy the files to the Windows partition?
I'm running GSS 3.3 RU2
0
↧
↧
Ping transmit failed. Dell OptiPlex 7460 AIO, Dell Latitude 5400
I need a solution
OptiPlex 7460 AIO
Processor - Intel(R) Core(TM) i5-8500 CPU @ 3.00GHz
RAM - 16GB
OS - Windows 10 Pro
Latitude 5400
Processor - Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
RAM - 16GB
OS - Windows 10 Pro
Symantec Ghost 12.0.0.8023
Trying to image new Dell OptiPlex 7460 All-in-ones as well as some Dell Latitude 5400s. All updates for windows as well as drivers and firmware are up to date, there are no driver conflicts. When trying to map the images to a network drive (I have no information about the specs or build of the server, sorry) I am met with "System error 1231" saying the network location cannot be reached. I am able to ping the server via windows command prompt but not through ghosts command prompt. All pings other than the loop-back address are returning a transmit failed, general failure.
I am able to ping the server though other PCs i have available in ghost, just not these specific computers.
Any help is appreciated! Thanks.
0
↧
Bluescreens after image deployment
I need a solution
I've been struggling with this issue (as my post history shows) for a long time. Now it's time to create a new image and I'm running in to the same sort of issue. When I sysprep a machine to capture the image, everything goes fine. After it captures, the machine boots into OOBE. No issue there. However, if I deploy the captured sysprepped image with GSS, after the image is laid down, the machine boots to a blue screen with a registry error 0xc000000f . When I boot into the machine from a USB drive and open a command prompt, I run notepad and see that GSS is writing the unattend file and aclient.cfg to the system reserved partition.
Here's what I see in a cmd window after the image is deployed:
M:\>M:\Ghost\ghost64.exe -CLONE,MODE=RESTORE,SRC="Z:\Sysprep\W10NEW\W10SYSPREP.gho",DST=1 -sure
M:\>RDeploy\Windows\x64\firm.exe copy ".\Temp\d5002194.cfg""d1p*:\aclient.cfg"
Copy .\Temp\d5002194.cfg d1p1:\aclient.cfg
\aclient.cfg copied successfully
Copy .\Temp\d5002194.cfg d1p2:\aclient.cfg
\aclient.cfg copied successfully
M:\>if "0" == "0" GOTO :EOFCfg
M:\>RDeploy\Windows\x64\firm.exe copy .\temp\5002194.xml d1p*:\windows\panther\unattend.xml
Copy .\temp\5002194.xml d1p1:\windows\panther\unattend.xml
\windows\panther\unattend.xml copied successfully
Copy .\temp\5002194.xml d1p2:\windows\panther\unattend.xml
\ - This is where it cuts off and the machine reboots but I assume it says it was copied successfullyfirm.exe is copying the aclient.cfg and the unattend.xml to 2 partitions - I'm not 100% sure that this is what is causing the blue screen, but how do I make it stop doing that and make it just copy the files to the Windows partition?
I'm running GSS 3.3 RU2
0
↧
Issues with ipxe failing to boot
I need a solution
Hi, We recently upgraded to 3.3 ru2 And installed the ipxe adons to try and use 2 servers have worked fine with no issue They boot to ipxe and image The servers are running server 2016 with full version of sql The 3rd server is failing to boot to ipxe - it keeps coming up with an error pxe-e53 I tried searching and tried some of the solutions but no joy Pxe works and boots a machine to winpe and images When we set it to ipxe it goes through the process but as its about to start pulling the winpe it fails with an error and boots to windows All 3 servers are identical- all running same version of the console and the pxe and pxe utility I have recreated a new pxe boot file using the ipxe option and saved it to the pxe config utility and checked it's the correct one being used to connect to by the pc Any ideas would be much appreciated Thanks This is a selection on the error from the log file 2019-08-15 09:23:45.9845|ERROR|Altiris.DSSDK.Server|GetPxeBootInfo : Exception while GetPxeBootInfo executing Input string was not in a correct format. 2019-08-15 09:23:46.1876|ERROR|GetPxeBootInfo.GetPxeBootInfo|Request : 107B441AFDA6P1210288128 2019-08-15 09:23:46.3126|ERROR|GetPxeBootInfo.GetPxeBootInfo|Failed to read PXEBootInfo Error Message: Input string was not in a correct format. Stack Trace: at Altiris.DSSDK.Server.GetPxeBootInfo(String resourceUUID, String resourceMacAddress, String resourceSerialNumber, String resourceIP) at GetPxeBootInfo.GetPxeBootInfo.Page_Load(Object sender, EventArgs e) 2019-08-15 09:24:32.4869|ERROR|Altiris.DSSDK.Server|GetPxeBootInfo : Exception while GetPxeBootInfo executing Input string was not in a correct format. 2019-08-15 09:24:32.5025|ERROR|GetPxeBootInfo.GetPxeBootInfo|Request : 107B441AFDA6P1210288128 2019-08-15 09:24:32.5025|ERROR|GetPxeBootInfo.GetPxeBootInfo|Failed to read PXEBootInfo Error Message: Input string was not in a correct format. Stack Trace: at Altiris.DSSDK.Server.GetPxeBootInfo(String resourceUUID, String resourceMacAddress, String resourceSerialNumber, String resourceIP) at GetPxeBootInfo.GetPxeBootInfo.Page_Load(Object sender, EventArgs e)
0
↧