Hello,
GHOST EXECUTABLE STATISTICS REFRESH RATE ARE NOT REAL TIME?
Daniel Reis
Hello,
GHOST EXECUTABLE STATISTICS REFRESH RATE ARE NOT REAL TIME?
Daniel Reis
I am new to the GSS 3.x version of the Ghost Console and have a question on creating a Automation package to push to clients. When it request the 'Automation Agent Location" I am not sure of whether I should choose 'Remote" or 'Local'. I want to be able to create/push images to clients from the server without having to visit each client to manually boot from a ghost boot device.
Thanks for any help and advise,
Art W.
I am trying to capture and image using GhostCast Server for the Dell E7440 AIO. Normally on these newer Dell systems I have to install the drivers for the network card as part of the WinPE 4.0. I have added all the Intel drivers for the I219-LM to the environment and also tried using drvload from a command prompt to do it manually. I cannot get the network card to come online. I have tried loading just about every version of this network driver without success. Any ideas or things to try?
I am trying to create an image of a Linux 6.7 OS with the 3.1 Suite.
I am able to create an image, but it takes ~2 hours to create. It seems like it is making a bit-for-bit image instead of compressing the image. The image I created was ~400GB large! I was expecting to see a ~4GB image size that takes 5-10 minutes to create.
I am wondering if the system file type has any bearing on the image creation... such as xfs vs. ext4. Does xfs slow ghost down?
Are there certain settings to select, in the Boot Disk Creator, for Linux images?
Some guidence with setting up, and creating, a Ghost boot disk would be greatly appreciated.
Just installed G3.1 manged to log onot Ghost the the PXE server, once I restarted the server the PXE servcies fail to start get Error 1068 dependency service or group failed can't find any resolution has anybody had this issue befroe.
Hi all,
We have started setting up computers and jobs in Ghost Solution Suite 3.0, making images for some Windows 10 deployments that are going to be coming up right away and we found out from our Microsoft rep about the new Provisioning Packages feature in Windows 10 that is supposed to remove the need for imaging, but instead makes it sound like is just going to be messing with our MAK and KMS activation counts each time we need to redeploy an image to a machine. Is anybody dealing with issues imaging Windows 10 machines that use a KMS server? Anything different than in years past? Is the Provisioning Packages feature something that we can use with Ghost Solution Suite or are there any options in Ghost Solution Suite 3.0 to combine the two effectively?
Thanks!
This is more of a general question about PXE Boot for the community. We have a few computers that do not exit on their own out of PXE boot if they don't have a job. They hang at "PXE-M0F: Exiting Intel Boot Agent.". The only way to exit out of the screen, is to use "ALT+CTRL+DEL". I'm just curious if others if experienced the same thing and if using automation folders on computers that are having an issue with PXE, would be a fair option? We'd like to use PXE where we can.
Dear,
I try to do a custom install on a Windows Serverr 2012 R2 (until now for Testing-Purposes only, thank God!)
Installed SQL Express (with named Instance "GSS"), Management Studio, SPs and Updates für SQL prior to GSS-Installation to put the SQL-Instances-Path to antother Drive (Server-HDD has C: for System and D: for Data, SQL-Instances-Path is D:\SQL-Inszanzen (German)).
After Installing SQL I start GSS-Setup and chose "Custom".
- Ghost File-Server-Path: D:\GSS
- GSS-Server on zhis Computer
- Install-Path (again) D:\GSS
- SQL-Server ist found, Database-Name changed to GSS
- Windows NT Authorization
- PXE-Server on this Computer, Path D:\GSS
- Direct Connection from Client to GSS via IP
- Console on this Computer
- Klick on "Install"
And then in happens: "UpgradeUtility.exe" crashes and the Installation does not start.
I can reproduce this many Times. What is it? Any Ideas?
ONE Time with in my Opinion exactly the same setting it worked and GSS installed, but that Test-Installation is broken due to "too much testing", so I have to do an new Installation.
Thanks in forward!
TJ
Dear,
having worked with GSS 2.5 and PXE-Boot of PC-Dos for many years, I actually test GSS 3.1 in proparation of an Windows 10 Rollout.
What I see is that PC-Dos-Boot took "a few seconds" while the WinPE-Boot tooks "a lot of minutes".
And I´m only testing GSS with one Client, what happens during a Rollout of about 230 PCs that have to be booted nearly contemporaneous?
What are other Upgraders tinking / doing about this Question?
______________________________________________________________________________________________________________
My next Task is to rollout my Win10-Image to the above mentioned 230 PCs (now Windows 7) and afterwords restore the Windows-Configuration (PC-Name, IP-Config, Domain-Join, etc.) For the second Point (restoring) I need GSS 3.1 because GSS 2.5 can´t handle Windows 10, but I could roll out my Image with GSS 2.5 and fast PC-Dos-PXE-Boot. Why isn´t that a good idea?
TJ
We are running Ghost Solution Suite 3.0 Build 1246
We sent a job to install automation partition to a Windows10 client. Job states it finished successfully, however client will not boot into Automation Partition - it boots into the production environment.
Does our version support Windows 10 clients?
Dear,
I need a little clarification:
When I create an Image with Sysprep in GSS 2.5 the Master-PC is sysprepped and the the image is created. That
- leaves the Master-PC behind as a sysprepped PC
- allows me to distribute this new image even with a manual Ghost-Cast-Session
In GSS 3.1 this seems to be done in two steps?
When I create an Image with Sysprep in GSS 3.1 the Master-PC seems to be not sysprepped before/after/during the creation of the image. In fact the Master-PC come´s up almost "untouched" after the Image-Creation.
When I distribute that Image with a GSS 3.1-Job an DO NOT activate the two checkboxes "Configuration-Task after Imaging" and "Reboot to Production" the new PC comes up with the same Name, IP-Adress and even Domain-Membership the Master-PC has had.
When I distribute that Image with a GSS 3.1-Job an DO activate the two checkboxes "Configuration-Task after Imaging" and "Reboot to Production" the new PC comes up sysprepped.
So: What das exactly happen on what PC (Master/Target) on which Point of the process?!
Thanks in vorward!
TJ
Hi,
I created an image with the new version of Ghost 3.1. The image was created using WinPE 5 and to be sure I did it twice. My problem is that when I try to deploy the image created previously, using WinPE, I get an error:
“Internal Error 8027
An Internal inconsistency has been detected. “
I tried to deploy the image with the console and with Ghostcast but I ended up with the same result.
Any ideas ?
thank you
Dear,
how can I change the Computer-Description for one or more existing Client-PC´s?
I can Change Computer-Name, Domain, IP and so on but I see no Input-Box for Computer-Description, is that right?
Also in the Smaple-Import-File I can find no field for Computer-Description, even if that would ony help for new but not for exsiting Clients.
I have some Applications that group my PCs according to the Description, which, in my case, contains the Building the PC is located in, while the PC-Names do not contain this info.
Thanks in forward!
TJ
Hello,
I'm using SCCM 2012 R2 to deploy a TS that contain gdisk32.exe /DISK:ALL /diskwipe. This command fail with the error "cannot lock disk". The way I'm loading the ts is Boot to PXE and start the TS, so the system HDD isn't used. Why can't I lock the disk?
My goal is to create a TS that will wipe all physical disk and do various configuration before shipping the computer to recycling facilities.
Thank you!
Doe anyone have any good documentation on deploying software to Mac's using GSS 3.1?
I created a boot disk with the "Boot Disk Creator" (bootwiz)
I am trying to boot to a Win8 UEFI safeboot computer and it will not boot to the USB.
If I disable safeboot, can I still take an image of the laptop?
I have Windows 8 computers running UEFI with safe boot.
I created a bootable, stand alone USB with the bootwiz to take backups with them.
With UEFI mode enabled the computers will not boot to the USB.
When enabling legacy mode I can boot to the USB.
If I take an image of one of these computers in legacy mode, will I be able to apply that image to another computer or back to the same computer?
Will I be able to do something like:
Will this work? How do I image UEFI safe boot computers with the bootable USB.
After installing a new 10gig Network card in our GSS server (running Windows 2012 R2) and changing the static IP from the old nic card to the new one.
After that, GSS console fails to launch with "Unable to connect to the Symantec Ghost Solution Suite DB Management Service"
"Unable to connect to the database. Would you like to try to open a different site?" And only "Default" is listed.
GSS, PXE & SQL Express DB are running all on the same server.
What is the proper way to switch to switch to a new network card? Would running the installer again fix the issue?
Thanks.
I have installed GSS 3.1 server and console on server 2008 R2. I have created a WinPE 5.1 automation package. When I try to install the automation package to clients (Win 7 Clients) by selecting install automation folder, the job starts but just shows "Sending package 'C:\Program Files *x86)\Altirs\eXpress\Deployment Server\AutoFolderPkgs\WinPE 5x AUtomation\X64\AF_WinPE 5x Automation.exe'..." It never installs and just stays showing this status several days until the job is deleted. I haven't been able to find the reason this is happening. I am new to GSS 3.1 and sure I have not set something up correctly but can't find it. Thought I followed the instructions given in the Installing Automation Package video.
Any help would be greatly appreciated.
Art W.
We are testing the Ghost Solution Suite 3.1 and having a problem with HP Z240 workstations.
The image creates fine but when we go to restore the image on a machine, we received a 19330 error - An Internal Inconsistency has been detected.
When we look at the ghosterr.txt file the message says EstimateFatClusterUsed: Unknown fat_type: 0
Any ideas?
Oh, there is no RAID in this system.