I’m trying to create an image using multicast with just the standard tools. I have formated a flash drive with a gpt partition and can get ghost to boot. The issue occurs when I connect to my session using multicast. All I can see is the OS Volume which I know is not my hard drive. On all new Dell’s their is no option for legacy boot. I use to be able to turn the legacy boot options on and see the hard drive, now I can’t when the flash drive boots uefi. This image is a gpt UEFI formatted image for Windows 10. Does anyone have any ideas? I’m grasping at straws.
Reverse imaging can be used to update antivirus and malware definitions, however, UEFI cannot perform this task as BIOS can perform it.
When reverse imaging UEFI VMs, consider the following:
Reverse imaging UEFI VMs can only be done manually using P2PVS.exe, using either:
○ Command line
I have run 1803 to 1903 with 11.3 installed without issue after turning pre-boot off for 3 logins, but now testing 1909 the upgrade is failing when going 1803 to 1909, on devices not running SEE 11.3 the upgrade goes fine.
is 1909 not supported for this yet? I see only 1903 listed in this link:
I’ve got a whole bunch of Windows Server 2012 systems, running SEP 14.2.4814.1101.105, “basic protection for servers” package.
Some of them have rebooted unexpectedly, due to SEP:
The process C:Program Files (x86)SymantecSymantec Endpoint Protection14.2.4814.1101.105BinccSvcHst.exe (SERVERNAME) has initiated the restart of computer SERVERNAME on behalf of user NT AUTHORITYSYSTEM for the following reason: Legacy API shutdown Reason Code: 0x80070000 Shutdown Type: restart Comment:
For most of the problem clients, this has only happened once that I’m aware of, either when the SEPM server was rebooted, or the SEP Master Service was restarted, e.g. for an upgrade to SEPM. Some of those were several weeks back, and one was this morning.
For one problem client, this happens every single time the master service restarts or the SEPM server is rebooted – I can replicate at will by simply restarting the master service on the SEPM server or rebooting the SEPM server, then waiting a couple minutes for the SEP client to trigger a reboot on the problem client.
My current plan is to do a full uninstall, reboot, run cleanwipe, reboot, and install the latest client package on the one really bad problem client, and seeing how things go.
For the other clients, scheduling downtime for many of them is difficult, so I’m wondering if this is a known bug, if there are workarounds, or what.
Not sure exactly where to look for help on this so that is why I am posting here. I am using ghostcast server version 18.104.22.16818 and am having difficulties imaging a new windows 10 laptop. Before we had laptops that allowed Legacy boot options and we were able to create an image no problem for those. However we now have a few new ones that only allow UEFI boot which may possibly be the issue I am having. So I syspreped my machine and that went fine but when I boot to a usb disk with UEFI on the client and get to the point of selecting a my disk, the size of the drive is only 150MB. The drive is an SSD that is 256GB. For some reason it is not seeing the full disk only a small parition of it. Does anyone know if this is due to using UEFI or some other reason? ANy help on this would be appreciated. Thanks.
I have a fairly rudimentary job that had been working flawlessly to perform a scripted install of Windows 10 1903:
- Erase Disk
- Partition Disk
- Install Windows
- Boot to Production
- Join Domain
Since upgrading to 8.5 RU3, my Windows install jobs are now getting stuck at “Boot to Production”, which times out after an hour. The PC has a working install of Windows 10 1903, but the agent was not installed, so it’s never able to communicate back to the NS that it successfully booted into production.
The organisation I’m working for are trying to remotely upgrade a great mixture of desktop and laptop machines to Windows 10. Many of our devices are failing to build at the reboot to pxe stage. We’ve found this was due to an incorrect patch installed at imaging stage, many devices aren’t set to boot from network in the bios. While we know how to fix this for individual devices, I was wondering if anyone knows how we could get a script going in altiris to run on multiple machines to detect only the devices with the wrong boot order. Many thanks in advance.
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.