Quantcast
Channel: Symantec Connect - Ghost Solution Suite - Discussions
Viewing all 1315 articles
Browse latest View live

Is it still possible to make a DeployAnywhere CD?

$
0
0
I need a solution

Using the latest 3.1 version, how to create a DeployAnywhere CD? 

The instruction located at https://support.symantec.com/en_US/article.TECH110135.html are no londer valid.

Thank you.

0

"User Supplied" PXE boot disk instructions?

$
0
0
I need a solution

I am unable to find solid instructions for building a "user supplied" PXE boot image.

Specifically, we're using PXE boot with WinPE images successfully, but those images were built within the boot disk creator.  Before we upgraded to GSS 3.1, we were using a Linux PXE server and we leveraged the PXE version of PMagic for troubleshooting and general tech work as well as booting the Ghost client.  The old version of GSS didn't support UEFI/Secure Boot, so we were happy to upgrade to the new environment.

Now we're able to use the Altiris server for Ghost, and the latest PMagic versions are Secure Boot compatible.

I have the latest PMagic PXE files, but for the life of me I can't find good documentation on turning them into a "user supplied" image for Altiris.

Any hints?

Thanks!

0

Maximum Throughput

$
0
0
I do not need a solution (just sharing information)

Hey Folks,

I may be coming from a somewhat outdated approach, but I'm looking to help inform myself of what I can't seem to find on the interwebs. I use Ghost64.exe from within WinPE_x64 to pull a 40gb -Z1 image over the wire. It is taking about 8-10mins to complete, and I am trying shave that time down to about 4 or 5 minutes. I feel like Ghost is holding me back, the Transfer Speed flattens out at around 3900-4100 MB/MIN. Does anyone know what the absolute Max MB/MIN Ghost will do?

If I put the Server and the Client on a "dumb" switch and assign 192.x.x.x addresses I can get the image to go at around 5122 MB/MIN.

According to calculations we should be able to obtain 8000 MB/MIN. Has anyone really seen this kind of speed with Ghost from WinPE. I can't seem to find the limiting factor.

Thanks for listening and responding

0

GSS 3.1 Imaging Negative Number Errors

$
0
0
I need a solution

We are testing GSS3.1 for pushing Win7 images in our environment in an attempt to move from GSS 2.5.1

We have the DAgent installed in the image, and the image is sysprepped prior to being backed up.

We push the image and config with a job, and we get the following errors:

"Error -2147463168 during configuration process", status code -214746318, module Win32

or

"There is no such object on the server", status code -2147016656, module Win32

My questions are:

1) what do these errors actually mean?

2) is there an OU depth limit that GSS3.1 can put the machine into?  We can get rid of the second error above (-2147016656) by using 2 modify config tasks.  The first to put it in a folder in our domain one level deep, the second to move it where we want.

3) we are deploying the Automation folder as part of the task after the modify configs, and sometimes it reports a success on the step, but the console says it is not installed when getting the properties of the object.  Should the Automation folder be in the image?

0

Cloning with UWF enabled gives WMI Connection error

$
0
0
I need a solution

Hello,

Long time listener, first time caller. I am trying to create a Windows 8.1 Industry image with a shell and UWF. The problem is, when I deploy the new image and open Embedded Lockdown Manager, I get an error that says:

"Not found."

and

"A WMI connection was made to the remote device but the system WMI providers could not be found. Make sure all WMI providers and the WMIv2 packages are installed on the remote device and try again."

While I see the control to toggle "Enable Unified Write Filter" I cannot press it and it is greyed out. Every other facet of the image is working well. I am not sure how WMI or a remote device factors in the equation. Before I added UWF, the image was running how I wanted. 

Has anyone encountered this before? I would appreicate any suggestions for a fix.

Thanks,

Yusif Nurizade

0

New MP5 - notification problems and do I need to do anything?

$
0
0
I need a solution

Hi - I heard that there is now an MP5 available for Ghost 3.1. As a user under maintenance why don't I receive notification that new software is available? Had I not had a case open and been talking to Symantec support I probably would not know about it unless I run into it by accident. I think I came across MP4 in the same manner.

Also - do I have to redo my automation folders or anything else after I upgrade?

Thanks!!

0

an extended error has occurred

$
0
0
I need a solution

Hello,

we have been imaging fine without issue but just got these new win 10 laptops and keep getting the error "an extended error has occurred" while trying to deploy the agent.

Any help would be great!

thanks

0

Unable to create image

$
0
0
I need a solution

I'm running into a strange problem when trying to image a computer.  I'm currently using GSS v3.1 Build 837, Maintenance Package 5.
And, in case it's relevant, I am trying to image a Dell Optiplex 7040 (with the Skylake processor).

I have added WinPE 4, 5x, and 10x to the PXE server, and have added all the necessary NIC drivers for the system - both Windows 7 and Windows 10 versions.
I have also been using the program to successfully image other models.

My first attempt to image this computer using my existing Boot Menu option resulted in the PXE boot not being able to get an IP from the DHCP server.  This is when I added NIC drivers for Win10, but I still get the same result.

After some reading, I decided to create a Boot option for WinPE10 with the updated NIC drivers.  This took me further in the process.  I get an IP from DHCP, and the Ghost session starts.  But within a couple of seconds, I get the following "Usage Error 662.  Cannot create image file...."
The other thing which I have never noticed, is at the bottom of the is says 'Data will be compressed - this will take longer'.  I don't recall ever seeing this, even when using just Ghostcast.

Thinking it could be something with this specific model computer, I decided to try imaging a computer I've made many images with - using the new WinPE 10 boot options.  Same result - Usage Error 662.

I have checked permissions and checked available space.  I don't know what to do.

Any help would be appreciated.

0

Ghost32 Error 770 Virtual disk cannot be created

$
0
0
I need a solution

When trying to convert a GHO image to a VMDK image on a mapped drive, the process fails with the following message:

ABORT: 770, Virtual disk cannot be created on destination filesystem as it cannot seek during write, e.g. http.

I'm using Ghost32 to do this conversion with the following command line:

ghost32 -clone,mode=restore,src=Image.GHO,dst=z:\Image.vmdk -batch -sure

This command works fine if the destination of the VMDK file is a physical disk, but if Z: is mapped to a shared folder on another PC, it fails.

(And yes, I have full read/write permissions on that shared folder.)

​Any suggestsions?

0

GSS 3.1 Remote Agent Installer Reproducable Crash

$
0
0
I do not need a solution (just sharing information)

When using the Remote Agent Installer in GSS3.1 MP5, I am able to reproduce a crash every time.

I select to Add a computer, navigate my AD tree, highlight one or more computers so their name appears in the Computer Name box, click the "UP" arrow at the top, reselect "Entire Network" and then I get this:

GSS31Error.png

100% of the time I do this.  I know the work around is easy (click OK), but its still an issue

0

GSS3.1 Database Error

$
0
0
I need a solution

I have received 2 of this error already today:

GSS31DatabaseLock.png

It reads:

Database error:

Transaction (Process ID 70) was deadlocked on lock resources with another process and has been chosen as the deadlock victim.  Rerun the transaction

Retry/Cancel

I have been having an issue all morning with all of my objects going grey in the console, then all of them coming back up for about 30 seconds, then all of them going grey again.

0

Automation Folder vs Partition question

$
0
0
I need a solution

I'm just learning to use GSS 3.1, and I don't understand the Automation Folder vs. Partition.  I want to install a FOLDER, so that when the deployment agent needs to run an imaging job it can load a PE boot disk from said folder and automatically carry out the task.  The only option I seem to be able to create is the Automation Partition - so every time a PC in one of my classrooms reboots, you get a 30 second delay where the user is presented with a choice between Windows and the Automation Partition.

I would assume there is a way to avoid this behavior, but when I go through the Boot Disk Creator wizard I have no option to change the settings regarding an Automation Partition.  I can create new ones, but as far as I can tell they're all going to be fully blown partitions, and not just a folder that gets called on when necessary.   Am I understanding all this correctly?

Thanks!

0

GSS 3.1 Hangs on Installing Automation Folder from Right-Click Menu

$
0
0
I need a solution

Title says it all really - our technician that supports the GSS server tells me this is a known issue since back in the summer.  When you right-click on a machine record and go to Advanced -> Install Automation Folder, the GSS console freezes up and you have to kill the process.  Scheduling an app install through the Job Wizard to do this works just fine.

We've restarted the server, cleared the C:\Windows\Temp and our individual user \AppData\Local\Temp directories per a previous post in this forum that went unresolved in June.  The thing is, I swear I've used this feature before without trouble, but something is definitely not working correctly now.  Any advice would be most welcome, thanks!

We're on GSS 3.1 (Build 607, MP 3).

0

Restore Configuration after Update from Win 7 to Win 10

$
0
0
I need a solution

Dear,

I have about 250 machines, connected to GSS 2.5 at the moment.
This summer I have to update this machines to Windows 10 (same Hardware, InPlace-Upgrade).

What I plan to do is:
1. Installing GSS 3.1-Server
2. Installing GSS 3.1-Client on my existing Win 7 machines (for collection Configuration-Info to GSS 3.1-Server)
3. Imaging all 250 machines with Win 10-Master-Image
4. Restoring the Configuration (only IP, Description, Domain, etc.; no User-Settings) to the "new" Win 10 machines

I´m testing a while but I can´t find the way to restore the Configuration collected from Win 7 to the Win 10 machines:
May be someone can give me a hint? Has this to be done within the Image-Rollout-Job? Or can it be done separately?
Do I have to do something to COLLECT the information froom the Win 7 machines? Or ist just installing the GSS-Client and waiting a little enough?

Thanky in forward!

TJ

0

When does Sysprep happen? (GSS2.5 - GSS 3.1)

$
0
0
I need a solution

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 (Non-Configured) PC after Image-Creation
- allows me to distribute this new image even with a manual Ghost-Cast-Session (no Automation)

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" (still Configured) 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.

So: What does exactly happen on what PC (Master/Target) on which Point of the process?!

Thanks in vorward!

TJ

P.S.:

Just tested: Distribute my above mentioned Image with Sysprep with manual Ghost-Cast to another PC: Same IP, same Name, seems like no Sysprep has been done, although I checked the Boxes when Creating the Image.

When I distribute exact this Image with a GSS 3.1-Job, also with checked Sysprep-Boxes, the Traget-Machine ends up as sysprepped.

So it seems to me that Sysprep is only done during the Distribution-Process but not during the Creation-Process of the image?
If this ist the Case: For what reason I have Sysprep-Checkboxes in the Image-Creation-Taks? Confused...

0

Sysprep Windows 10 Education

$
0
0
I need a solution

Dear;

I still try to create a sysprepped Image of my Windows 10 Machine.

I have to mention, that I do not use Windows 10 Professional or Windows 10 Enterprise but Windows 10 Education. The Education-Edition is mostly like the Enterprise-Edition but has a few other Settings (e.g. no Cortana) and ist sold only to Schools etc..

When I try to capture an Image I use GSS-Sysprep-Setting of Windows 10 Enterprise (x64). Everything seem´s to work fine, an Image is created, but when my Master-Machine comes back up, it has still the same Name, same Workgroup, ... ,. Also when I distribute that Image to another machine, this other machine has the same Name and Workgroup like my Master (even when some Screens in the first Boot of this other Machine looked like Sysprep has worked, strange somehow, like "Half-Sysprepped")
Anyway: That leads me to "Sysprep has not worked".

Does anybody know: Is there a difference in sysprepping Enterprise vs Education?
May be I simply use the wrong Settings (for only Enterprise ist available in GSS but Education is not)?

As I don´t know very much about sysprepping: Where could I start to investigate what´s going wrong during the Sysprep-Attempt?

Thanks in forward!

TJ

0

How to identify if systems are booted into UEFI or BIOS mode.

$
0
0
I need a solution

I have just upgraded to GSS 3.1 MP5... I should have posted this long ago but worked around it instead.  Looking for a way of programatically indentifying wether a system is booted into UEFI or BIOS mode.  On USB drives I am able to use the Microsoft recommended method of using a command to query a value in the registry of the booted winpe environment for a value.  The microsoft method is found at the followiing URL:

https://msdn.microsoft.com/en-us/library/windows/h...

The problem is that the value referenced above is not present in any Altiris or GSS registry when WinPE is running in UEFI mode.

We have some scripts that run in WinPE that depend on wether the system is being imaged in UEFI mode or Legacy mode and the scripts behave differently based on the boot mode.  Any assistance is greatly appreciated.  Thanks :)

0

Cannot Deploy Image to Desired Partition From Local Drive

$
0
0
I need a solution

I'm trying to image an HP ElitePad 1000 running Windows 8.1.

I've imaged these many times using over the network using pxe. Now I need to develop a method of deploying from a USB thumb-drive.

The image needs to be deployed to a certain partition on the tablet otherwise it completely bricks it and I need to reestablish the partitions.

When I deploy over the network I am able to select drive 1 and partition 4 from the Ghost server and it deploys without issue. However, when I attempt to deploy localy using a thumb-drive it will not complete.

I boot using a WinPE thumb-drive. This opens a command window from which I start Ghost64.exe.

When I try deploying Local => To Disk => From Image and select the required drive and partition a dialogue box pops up stating that it will convert the partition from FAT32 to FAT Proceed y/n. Upon selecting yes the imaging process begins. After a few seconds Ghost stops, closes and in the comand window it states: ABORT: 8027, A GeneralException occured. Upon investigation this suggests that the target pertition is too small for the file. This cannot be the case as the target partition is 48485Mb and the image is less than 20Gb.

If I try to deploy Local => To Partition => From Image the destination partition is not available in drive 1.

Please help.

0

Can't join domain after deploying image

$
0
0
I need a solution

I will try to keep this brief.

My task sequence in GSS 3.1 build 607, Maintenance Package 3 is this:
1 - Create Disk Image.  This is my base image with updates applied
2 - Run script which includes deleting logs and running Sysprep OOBE.  I'm using /generalize /oobe /quit /unattned...unattend.xml
3 - Create Disk Image.  This is the sysprepped image.

I am also utilizing SetupComplete.cmd (Windows\Setup\Scripts) to remove the Altiris agent.
I am using DHCP on the Ghost server, but the machines I deploy to will have statice IP's.
I can deploy the image using Ghost, and I can enter my static IP.  However, when I try to join the PC to the domain, I get the message 'Network path not found'.

I can ping all relevant devices and I can access the internet.

If I take GSS3.1 out of the equation and create my images manually, I do not have this problem.  This leads me to believe that there is some remnant being left behind by the Altiris agent.

Suggestions?

0
1482329430

Cannot Deploy Image to Desired Partition From Local Drive

$
0
0
I need a solution

I'm trying to image an HP ElitePad 1000 running Windows 8.1.

I've imaged these many times using over the network using pxe. Now I need to develop a method of deploying from a USB thumb-drive.

The image needs to be deployed to a certain partition on the tablet otherwise it completely bricks it and I need to reestablish the partitions.

When I deploy over the network I am able to select drive 1 and partition 4 from the Ghost server and it deploys without issue. However, when I attempt to deploy localy using a thumb-drive it will not complete.

I boot using a WinPE thumb-drive. This opens a command window from which I start Ghost64.exe.

When I try deploying Local => To Disk => From Image and select the required drive and partition a dialogue box pops up stating that it will convert the partition from FAT32 to FAT Proceed y/n. Upon selecting yes the imaging process begins. After a few seconds Ghost stops, closes and in the comand window it states: ABORT: 8027, A GeneralException occured. Upon investigation this suggests that the target pertition is too small for the file. This cannot be the case as the target partition is 48485Mb and the image is less than 20Gb.

If I try to deploy Local => To Partition => From Image the destination partition is not available in drive 1.

Please help.

0
Viewing all 1315 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>