After I create the Ghost 3.0 boot disk for USB drive, what is the function in the disk(except imaging)?
Can I use gdisk and partitioning?
After I create the Ghost 3.0 boot disk for USB drive, what is the function in the disk(except imaging)?
Can I use gdisk and partitioning?
Not sure exactly where to look for help on this so that is why I am posting here. I am using ghostcast server version 12.0.0.10618 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.
Hello All,
I recently faced an issue with my Laptop running Windows 8.1.
I believe it came from leaving a bootable USB Stick inserted while the machine went to sleep.
However, after getting it woken up by pressing the power button once it came up with a Windows Screen telling (picture1):
***
Recovery
Your PC needs to be repaired
A required device isn’t connected or can’ be accessed.
Error code: 0xc000000e
You’ll need to use the recovery tools on your installation media. If you don’t have any installation media (like s disc or USB device), contact your system administrator or PC manufacturer.
Press Enter to try again
Press F8 for Startup Settings
***
Unfortunately neither “Enter” nor F8 offerns anything but the screen above.
I sticked to the Preboot Execution Menu, selected “Log Files” and found that there might be something wrong around data integrity (picture2).
Is there any way to convince the software to let the Laptop start?
My understanding is that the Endpoint Protection is not operating as expected leaving the Filesystem unreadable for Windows, resulting inthat screen for recovery.
It would be most appreciated if someone could point me to where to go with that. I at least need to copy some data off that SSD, I don’t mind for a full OS re-install later on.
MANY THANKS IN ADVANCE!
Cheers
Chris
We currently are using SEP 15 (hybrid with clients on 14.2).
Our policy blocks all access to the USB Class 36fc9e60-c465-11cf-8056-444553540000.
We’ve been carving out exceptions as needed and one of those of those devices in question is a vendor specific secure thumb drive.
Through initial testing I realized that allowing:
USBSTORDisk&Ven_Apricorn&Prod_Secure_Key_3z&Rev_0401*
didn’t do the trick and I needed to whitelist the parent device which was
USBVID_0984&PID_1409*.
This worked fine for months and then on October 9th these devices (along with clickshare and some others) began being blocked again despite nothing having changed. The policy has been through a few new versions, but the whitelisting of those devices hasn’t changed. No method of whitelisting I’ve tried seems to do the trick anymore so I’m not sure what I’m missing.
Any help or guidance would be appreciated.
We’re using SEPC’s feature, Connected Storage Devices, to block external USB drives on Windows machines, but I noticed I don’t see it mentioned for macOS. Is it possible to prevent external storage devices to be used on macOS devices as well? If not, then will this be a feature soon?
We have third-party virus scanning software for external devices such as USB disk, memory cards, etc and dvd . I was able to build a policies in Symantec Application and Devices Control that only the same media scanning software above will give read and write access.
The Problem I Can’t or Don’t Know How To Do This On DVD DC BD Devices Is there something that has experienced such a phenomenon or know how to solve it?
My Sysmantec endpoint protection manager ver 14.2.1 (14.2ru1).
server : Windows server 2012 r2 Datacenter
Hi,
I have a problem with new HP Elitebook G6 (but also with some HP Zbook G5 models) and the internal keyboards in SEE UEFI preboot screen.
Problem is that not every keystroke is recognized. I have to press sometime up to 4-5 times until it is recognized. Its not usable for users espacialy in the password field.
USB Keyboard works fine.
Legacy Bios Mode works fine, too. OS is Windows 10 1809
I tried a lot with several Bios settings, but could not get it work.
Any suggestions?
BR
Andreas
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!!
I learned long ago to never assume…so…
If I want to block USB devices I can add the USB class in Blocked Devices, right? Then, if I want to allow certain USB devices (such as human interface devices and individual USB devices) I can add those in Devices Excluded From Blocking. Right? Devices Excluded From Blocking will override the Blocked Devices class. Right?
Thanks.
The USB blocking policy was enforced. However, upon checking the events last June 23, 2019, SEP client was not able to BLOCK the USB device totally. Based on the Device Manager Message, if the USB device is plugged again, the device will be enabled.
Why does it fails to get the block device? Can some of you enlighten us on this?Please see screenshot below