Is this for me?

June 26, 2018, 4:36 pm

≫ Next: Transfer WinPE image to another server

≪ Previous: Ghost 11.0 - Internal Error 8027

$

0

0

I do not need a solution (just sharing information)

Hello community,

My team and I have been playing around with GSS for a short while now and we seem to be getting nowhere with what we are trying to accomplish.

We have a system that utilizes both Windows and Linux OS's that have built in automation for certain programs and an approved list of applications that can be allowed for security purposes. These systems do not and CAN NOT connect to an external (i.e. Internet) network but are connected internally only to each other. In the past our imaging process consisted of removing the hard drive and connecting it to a secured stand-alone workstation to either build the image or deploy it locally with Clonezilla. Once the image is created, a live image disk is burned and shipped to satellite offices for them to deploy on their systems.

From what I can gather GSS acts as a central management suite for an organization to backup & deploy machines connected to a network. Is it possible for GSS to be installed on a workstation and create an image of an attached external hard drive? As mentioned above there will be zero network connectivity between the workstation and the systems that we need to image, and no additional software can be installed.

Thank you in advanced.

0

---

Transfer WinPE image to another server

June 28, 2018, 6:10 am

≫ Next: Multicast cloning limit to 32 clients while using large GHO image file

≪ Previous: Is this for me?

$

0

0

I need a solution

We have 3 GSS servers in our environment, and instead of editing the WinPE image on each when we need to make a change, is there an easy way to export a WinPE image from one server and import it into another?

0

Multicast cloning limit to 32 clients while using large GHO image file

May 16, 2018, 8:00 pm

≫ Next: Question regarding Computer Name Range

≪ Previous: Transfer WinPE image to another server

$

0

0

I need a solution

Hi there,

I am using Ghost v12.0.0.8023 Corporate Edition and GhostCast Server v12.0.0.8023. 

We observed that with GHO image file of > 15GB, the maximum number of multicast clients allow to connect and cloning is 32 only. If using a small GHO image like (3-6GB GHO), it able to multicast to more clients, eg: 36 clients for our use-case. The setup is with Cisco managed switch and properly configured for IGMP and etc. All experiments done with same network and setup, just different GHO image size. From ghost logs able to see all clients did connected to GhostCast Server, but GhostCast Server only replied to 32 clients and no more. 

Would like to hear from Symantec whether there is limitation imposed or our setup issue?  

0

Question regarding Computer Name Range

June 29, 2018, 4:15 pm

≫ Next: Unable to boot to Windows Automation

≪ Previous: Multicast cloning limit to 32 clients while using large GHO image file

$

0

0

I need a solution

I've figured out how to modify my configuration to name my target pcs and add them to the domain.  My question is regarding the name range format.  I need to format it something like TEST###EXAMPLE, but it seems I can only affix the numeric range at the end.  Is there a way to format the numeric range in between alphas?

0

Unable to boot to Windows Automation

July 2, 2018, 8:08 am

≫ Next: Symantec™ Ghost Solution Suite 3.2 Release Update 7 (RU7) is now available

≪ Previous: Question regarding Computer Name Range

$

0

0

I need a solution

Background;

Running GSS 2.3 RU6

Server OK, installed DA agent to client PC, using boot disk creator created configuration for winPE as my clients are XP or Win 7. (via WAIK 3.1)

Using boot disk creator, created automation folder installer.

was able to install automation folder to client as I can see c:\boot folder

The Issue:

after creating task to create image of HDD, and after selecting "run now",  PC  reboots but fails to load winPE but boots back into OS (Win XP)

I include the file from autoutil,

I hope someone out there can tell me what is going on.

 

2018/07/02 15:07:32 autoutil(0fb8) I: ****************************************
2018/07/02 15:07:32 autoutil(0fb8) I:    Application Start:
2018/07/02 15:07:32 autoutil(0fb8) I:    (c:\boot\altiris\iso\autoutil.exe)
2018/07/02 15:07:32 autoutil(0fb8) I: ****************************************
2018/07/02 15:07:32 autoutil(0fb8) I:     Module:       'c:\boot\altiris\iso\autoutil.exe'
2018/07/02 15:07:32 autoutil(0fb8) I:     Command line: 'c:\boot\altiris\iso\autoutil.exe -q'
2018/07/02 15:07:32 autoutil(0fb8) I:     Using startup parameters from ini file:
2018/07/02 15:07:32 autoutil(0fb8) I:       'c:\boot\altiris\iso\autoutil.ini' - [LogFile]: Severity=d, Screen=false, Append=an, TimeStamps=C, ProcessIDs=mp, File='C:\autoutil.log'

2018/07/02 15:07:32 autoutil(0fb8) I: AutoUtil application version and architecture is '1.1.10400.20-x86'
2018/07/02 15:07:32 autoutil(0fb8) I: ParseCmdLine (sCmdLine='-q')
2018/07/02 15:07:32 autoutil(0fb8) D:     sCmdLine='-q'
2018/07/02 15:07:32 autoutil(0fb8) D:     sInstallTo=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sCopyFrom=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sCopyTo=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sBootDevice=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sSection=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sKey=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sVal=''
2018/07/02 15:07:32 autoutil(0fb8) D:     sIni=''
2018/07/02 15:07:32 autoutil(0fb8) D:     bGet=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bSet=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bSetAuto=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bSetProd=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bReg=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bUnreg=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bVerbose=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bCopy=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bQueryStatus=1
2018/07/02 15:07:32 autoutil(0fb8) D:     bBootDevice=0
2018/07/02 15:07:32 autoutil(0fb8) D:     bIgnore=0
2018/07/02 15:07:32 autoutil(0fb8) I: CClient::Create (sAppPath='c:\boot\altiris\iso', sInstallPath='', bSilent=0, bVerbose=0, bBootDevice=0)
2018/07/02 15:07:32 autoutil(0fb8) I:   Begin CClient::GetOSVer ()
2018/07/02 15:07:32 autoutil(0fb8) I:     Client OS version from GetVersionEx is 'WinNT-5.1.2600:Service Pack 3-x86' (5.1)
2018/07/02 15:07:32 autoutil(0fb8) I:     Client OS version from Registry is 'WinNT-5.1.2600:Service Pack 3-x86' (5.1)
2018/07/02 15:07:32 autoutil(0fb8) I:     Client OS version from Kernel (C:\WINDOWS\system32\kernel32.dll) is 'WinNT-5.1.2600.6532-x86' (5.1)
2018/07/02 15:07:32 autoutil(0fb8) I:   End GetOSVer - Using client OS of 5.1
2018/07/02 15:07:32 autoutil(0fb8) I:   Client OS type is NT
2018/07/02 15:07:32 autoutil(0fb8) I:   Client OS is 2000, XP or 2003, etc (5.*)
2018/07/02 15:07:32 autoutil(0fb8) I:     Client OS is XP (5.1) - use XP class
2018/07/02 15:07:32 autoutil(0fb8) I: CClient::CClient (bUseNativeBcdEdit=0, sBaseSection='NTLDR', sClientSection='XP', sVerb='open', sAppPath='c:\boot\altiris\iso', sInstallPath='', bSilent=0, bVerbose=0, bBootDevice=0)
2018/07/02 15:07:32 autoutil(0fb8) D:   Begin GetProdBootDrive (bInAutomation=0)
2018/07/02 15:07:32 autoutil(0fb8) D:   End GetProdBootDrive - returning 'C:'
2018/07/02 15:07:32 autoutil(0fb8) I:   Begin bcd::UsesNativeBootMgr (bVerbose=false, pWnd=00000000, sBcdEditPath='')
2018/07/02 15:07:32 autoutil(0fb8) I: - - bRedirectDisabled = 0
2018/07/02 15:07:32 autoutil(0fb8) D:           RunShellExecute - ShellExecuteEx (sFile='bcdedit.exe', sParam='/enum all') returned FALSE or hInstApp is < 32 (2), returning FALSE
2018/07/02 15:07:32 autoutil(0fb8) D:   -UsesNativeBootMgr - RunCommand returned false, exitcode=2
2018/07/02 15:07:32 autoutil(0fb8) I:   End bcd::UsesNativeBootMgr - returning false
2018/07/02 15:07:32 autoutil(0fb8) I:   Determine bcdedit path...
2018/07/02 15:07:32 autoutil(0fb8) D:     don't use native path - use installer path of 'C:\boot\altiris\iso\bcdedit.exe'
2018/07/02 15:07:32 autoutil(0fb8) I:   Determine bcd path...
2018/07/02 15:07:32 autoutil(0fb8) D:     bootmgr not detected - use explicit bcd path of 'C:\boot\bcd'
2018/07/02 15:07:32 autoutil(0fb8) I:  CClient::IniReadVariables (sFile='c:\boot\altiris\iso\autoinst.ini', sSection='NTLDR_VARIABLES')
2018/07/02 15:07:32 autoutil(0fb8) I:  CClient::IniReadVariables (sFile='c:\boot\altiris\iso\autoinst.ini', sSection='VARIABLES')
2018/07/02 15:07:32 autoutil(0fb8) D:     %MASTER_GUID% = '{e217309d-dead-beef-a315-001372be0d01}'
2018/07/02 15:07:32 autoutil(0fb8) D:     %MASTER_GUID2% = '{e217309d-dead-beef-a315-001372be0d02}'
2018/07/02 15:07:32 autoutil(0fb8) D:     %DESCRIPTION_AUTOMATION% = 'Symantec Deployment Solution Preboot Environment'
2018/07/02 15:07:32 autoutil(0fb8) D:     %DESCRIPTION_PRODUCTION% = 'Windows Production Operating System'
2018/07/02 15:07:32 autoutil(0fb8) D:     %DESCRIPTION_BOOTMGR% = 'Windows Boot Manager'
2018/07/02 15:07:32 autoutil(0fb8) D:     %FORCE% = ''
2018/07/02 15:07:32 autoutil(0fb8) D:     %MBR% = ''
2018/07/02 15:07:32 autoutil(0fb8) I:  CClient::IniReadVariables (sFile='c:\boot\altiris\iso\autoinst.ini', sSection='IF_CMDS')
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_BOOTDIR% = '@CMD.EXE|/D /C DIR /b "%INSTALL_PATH%"'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_BCDSTORE% = '@CMD.EXE|/D /C DIR /b "%BCD_PATH%"'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_ANY% = 'ANY'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_BOOTMGR% = 'BOOTMGR'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_OSLOADER% = 'OSLOADER'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_NTLDR% = 'NTLDR'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_PREBOOTLDR% = 'PREBOOTLDR'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_PREBOOTOPT% = 'PREBOOTOPT'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_TIMEOUT% = 'TIMEOUT'
2018/07/02 15:07:32 autoutil(0fb8) D:     %IF_BCDEDIT% = '@CMD.EXE|/D /C DIR /b "%INSTALL_PATH%\bcdedit.exe"'
2018/07/02 15:07:32 autoutil(0fb8) D:   Tokens:
2018/07/02 15:07:32 autoutil(0fb8) D:     %BCDEDIT_PATH% = 'C:\boot\altiris\iso\bcdedit.exe'
2018/07/02 15:07:32 autoutil(0fb8) D:     %BCD_PATH% = 'C:\boot\bcd'
2018/07/02 15:07:32 autoutil(0fb8) D:     %BCD_OPT% = '/store "C:\boot\bcd"'
2018/07/02 15:07:32 autoutil(0fb8) D:     %INSTALL_PATH% = 'C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) D:     %INSTALL_PATH_NO_DRIVE% = 'boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) D:     %PROD_DRIVE% = 'C:'
2018/07/02 15:07:32 autoutil(0fb8) D:     %BOOT_FOLDER_PATH% = 'C:\boot'
2018/07/02 15:07:32 autoutil(0fb8) D:     %MASTER_GUID% = '{e217309d-dead-beef-a315-001372be0d01}'
2018/07/02 15:07:32 autoutil(0fb8) D:     %MASTER_GUID2% = '{e217309d-dead-beef-a315-001372be0d02}'
2018/07/02 15:07:32 autoutil(0fb8) D:     %DESCRIPTION_AUTOMATION% = 'Symantec Deployment Solution Preboot Environment'
2018/07/02 15:07:32 autoutil(0fb8) D:     %DESCRIPTION_PRODUCTION% = 'Windows Production Operating System'
2018/07/02 15:07:32 autoutil(0fb8) D:     %{inject}% = 'C:\boot\altiris\iso\@inject@'
2018/07/02 15:07:32 autoutil(0fb8) D:     %{dot}% = 'C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) D:     %{iso}% = 'C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) D:     %%SRC%% = 'c:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) D:     %%DST%% = 'C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) I:   Member variables:
2018/07/02 15:07:32 autoutil(0fb8) I:     m_bIsAutomation     =false
2018/07/02 15:07:32 autoutil(0fb8) I:     m_bUsesNativeBootMgr=false
2018/07/02 15:07:32 autoutil(0fb8) I:     m_bUseNativeBcdEdit =false
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sVerb             ='open'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sAppPath          ='c:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sIniPath          ='c:\boot\altiris\iso\autoinst.ini'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sProdBootDrive    ='C:'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sInstallPath      ='C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sBcdEditPath      ='C:\boot\altiris\iso\bcdedit.exe'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sBootFolderPath   ='C:\boot'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sBcdPath          ='C:\boot\bcd' (not found)
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sDotFolderPath    ='C:\boot\altiris\iso'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sInjectFolderPath ='C:\boot\altiris\iso\@inject@' (not found)
2018/07/02 15:07:32 autoutil(0fb8) I:     m_bSilent           =false
2018/07/02 15:07:32 autoutil(0fb8) I:     m_bVerbose          =false
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sMasterGuid       ='{e217309d-dead-beef-a315-001372be0d01}'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sMasterGuid2      ='{e217309d-dead-beef-a315-001372be0d02}'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sBaseSection      ='NTLDR'
2018/07/02 15:07:32 autoutil(0fb8) I:     m_sClientSection    ='NTLDR'
2018/07/02 15:07:32 autoutil(0fb8) I: CClientNtldr::CClientNtldr (sClientSection='XP', sVerb='open', sAppPath='c:\boot\altiris\iso', sInstallPath='', bSilent=0, bVerbose=0, bBootDevice=0)
2018/07/02 15:07:32 autoutil(0fb8) I: CClientXp::CClientXp (sVerb='open', sAppPath='c:\boot\altiris\iso', sInstallPath='', bSilent=0, bVerbose=0, bBootDevice=0)

2018/07/02 15:07:32 autoutil(0fb8) I: ----- Start Query operation -----

2018/07/02 15:07:32 autoutil(0fb8) I: Begin CClient::IsInstalled (bForce=0)
2018/07/02 15:07:32 autoutil(0fb8) I:  bcd::GetOsLoaderIdentifier (sGuid='{e217309d-dead-beef-a315-001372be0d01}', sDescription='')
2018/07/02 15:07:32 autoutil(0fb8) I:    Begin bcd::GetOsLoaderObjects (v, sId='')
2018/07/02 15:07:32 autoutil(0fb8) D:           CreateChildProcess - CreateProcess (sFile='C:\boot\altiris\iso\bcdedit.exe', sParam='/store "C:\boot\bcd" /enum {e217309d-dead-beef-a315-001372be0d02} /v') failed with GetLastError=193, returning false
2018/07/02 15:07:32 autoutil(0fb8) D:         RunCommandRedirectToBuffer - CreateChildProcess (sFile='C:\boot\altiris\iso\bcdedit.exe', sParam='/store "C:\boot\bcd" /enum {e217309d-dead-beef-a315-001372be0d02} /v') failed with exitcode 193, returning FALSE
2018/07/02 15:07:32 autoutil(0fb8) I:    End bcd::GetOsLoaderObjects found 0 objects
2018/07/02 15:07:32 autoutil(0fb8) I: End CClient::IsInstalled - returning false
2018/07/02 15:07:32 autoutil(0fb8) D: CClientXp destructor called
2018/07/02 15:07:32 autoutil(0fb8) D: CClientNtldr destructor called
2018/07/02 15:07:32 autoutil(0fb8) D: CClient destructor called

2018/07/02 15:07:32 autoutil(0fb8) I: AUTOUTIL is returning 2 (EXIT_QUERY_NOT_INSTALLED)

2018/07/02 15:07:32 autoutil(0fb8) I: Ending application instance
2018/07/02 15:07:32 autoutil(0fb8) I:     Exit code: 2 (EXIT_QUERY_NOT_INSTALLED)
2018/07/02 15:07:32 autoutil(0fb8) I: ****************************************
2018/07/02 15:07:32 autoutil(0fb8) I:    Application End
2018/07/02 15:07:32 autoutil(0fb8) I: ****************************************

0

Symantec™ Ghost Solution Suite 3.2 Release Update 7 (RU7) is now available

July 3, 2018, 7:13 am

≫ Next: Ghost Solution Suite 3 Metrics (Request)

≪ Previous: Unable to boot to Windows Automation

$

0

0

I do not need a solution (just sharing information)

Symantec™ Ghost Solution Suite 3.2 Release Update7 (RU7) is now available.

Click the following link to access the release notes:

https://support.symantec.com/en_US/article.DOC11049.html

Feature	Description
Added support for Operating Systems	From this release onwards, following Operating systems are supported: ■ Windows 10 Redstone 4 ■ WinPE 1803
Added sample job to facilitate In-place OS upgrade to Windows 10 (version) and higher.	From this release onwards, you can use the In-place upgrade sample job to upgrade from Windows 7, Windows 8.1 and Windows 10 to Windows 10 Redstone1 and higher. For more information, refer to the following article: DOC11060
Deprecated features	From this release onwards, the following features are deprecated. ■ Chat feature

0

Ghost Solution Suite 3 Metrics (Request)

July 6, 2018, 10:23 pm

≫ Next: Are networked Windows 2000 computers supported?

≪ Previous: Symantec™ Ghost Solution Suite 3.2 Release Update 7 (RU7) is now available

$

0

0

I do not need a solution (just sharing information)

Hi everyone,

I'm writing an article on Ghost Solution Suite 3 performance, and I'm wanting to sanity check the sizing guidelines I'm proposing.

I'd appreciate it if you could run the SQL below on your GSS servers and PM me the results? 

use express

declare @dbsize int
declare @comp int
declare @jobs int
declare @histrows int
declare @histage int
declare @schedrows int
declare @schedage int
declare @statrows int
declare @statage int
declare @wincount int

select @dbsize = size*8/1024 from sys.database_files where type=0
select @comp=count(*) from computer

select @wincount=count(*) from computer where computer.os like 'Windows%'
select @jobs= count(*) from event_schedule
select @histrows=count(*), @histage=datediff(dd,min(complete_time),getdate())
from history_archive

select @schedrows=count(*), @schedage=datediff(dd,min(end_time),getdate())
from event_schedule

select @statrows=count(*), @statage=datediff(dd,min(complete_time),getdate())
from status_log_archive

select @dbsize as 'DB Size(MB)', @comp as 'Computers',@jobs as 'Jobs'
,@histrows as 'History rows'
,@histage as 'History Age'
,@statrows as 'Status Archive rows'
,@statage as 'Status Archive Age'
,@schedrows as 'Schedule rows'
,@schedage as 'Schedule Age'
,@wincount as 'Win Machines'

0

Are networked Windows 2000 computers supported?

July 11, 2018, 8:41 am

≫ Next: WinPE10 with Powershell Support

≪ Previous: Ghost Solution Suite 3 Metrics (Request)

$

0

0

I need a solution

Hello,

We are looking for a backup solution that is capable of backing up Windows 2000 and Windows 7 peer-to-peer networked computers to a centrl server. Can this be done with Ghost Solution Suite?

Thanks in advance

Tim

0

---

WinPE10 with Powershell Support

July 17, 2018, 3:49 am

≫ Next: GSS 3.1 - Programmatically executing jobs & retrieving job status

≪ Previous: Are networked Windows 2000 computers supported?

$

0

0

I need a solution

Hello,

I tried to add Support for Powershell in WinPE10 in WinPE5 everything is working fine.

But when i try to add the Depencies (Dependencies: Install WinPE-WMI > WinPE-NetFX >WinPE-Scripting before you install WinPE-PowerShell.) to the WIM I got an Error while creating the PXE Packages with the BootCreator.

2 Times Error Message: Folder not Empty

Creaton Failed.

I looks like there a some Files and Directories with a too long pathname.

0

GSS 3.1 - Programmatically executing jobs & retrieving job status

July 20, 2018, 2:31 pm

≫ Next: Virtual Machines not Appearing Online

≪ Previous: WinPE10 with Powershell Support

$

0

0

I need a solution

Hi,

I've set up some Image jobs for my client machines using the Ghost Solution Suite Console and now need to programmatically execute them. Does GSS 3.1 provide this functionality through some kind of an API or CLI, and if so will I be able to also query the status of job with it?

I dug through some other posts that mentioned being able to programmatically schedule tasks using axSched - can anyone confirm if this approach is viable?

0

Virtual Machines not Appearing Online

July 23, 2018, 10:42 am

≫ Next: Wrong driver?

≪ Previous: GSS 3.1 - Programmatically executing jobs & retrieving job status

$

0

0

I need a solution

Hello,

We've been using GSS successffully for about 2-3 years, but after applying a new license file in order to increase our license count, we are suddenly seeing some strange behaviour with physical machines vs. virtual machines.  We are running 3.2 RU6.

Phyical machines appear online and can be controlled as expected, but all virtual machines appear offline.  The agent installs are the same, the machines are on the same network, the same firewall rules apply (no logged packet drops), the client logs look identical between physical and virtual etc.

We have a support case currently open, but has anyone else seen this behaviour?

Thanks!

0

Wrong driver?

July 24, 2018, 12:30 am

≫ Next: PXE services are fine but WinPE Files fail to load during Preboot after selecting option

≪ Previous: Virtual Machines not Appearing Online

$

0

0

I need a solution

Gents,

I have been struggling with imaging and restoring two servers. The servers are not identical, but use the same network card (reported as intel i350)

ServerA boots PXE and starts imaging, ServerB hangs in "restarting DHCP". All posts I find point at a driver issue, but I do not understand how to platforms with the same NIC and the same WinPE can behave so different?

Cheers and thanks,

Max

0

PXE services are fine but WinPE Files fail to load during Preboot after selecting option

July 24, 2018, 1:12 pm

≫ Next: RU7 Upgrade Fails

≪ Previous: Wrong driver?

$

0

0

I need a solution

WinPE 10 build 1803, Ghost Suite 3.2 RU7

As per Wireshark Trace, boot menu loads but it fails to download files for PE when it shuold start (Client PC remains on PXE Menu options page):

Trivial File Transfer Protocol

Opcode: Error Code (5)

[Source File: MenuOption161\64\MenuOption161.efi]

Error code: Option negotiation failed (8)

Error message: user aborted the transfer

0

RU7 Upgrade Fails

July 27, 2018, 3:57 pm

≫ Next: How to setup Ghost Solution 3.2 to UEFI Dell 7060 Machines

≪ Previous: PXE services are fine but WinPE Files fail to load during Preboot after selecting option

$

0

0

I need a solution

Running Ghost Solution Suite 3.2 RU6 on 2012 R2 server, it connects to a SQL Server 2016 database.

When you run the RU7 update it fails part way through with the message "failed to connect with the sql server".  Installed the Microsoft update as mentioned here, https://support.symantec.com/en_US/article.DOC10866.html.  Rebooted the SQL server and still get the same error message when I try to run the update.

Any ideas?

0

How to setup Ghost Solution 3.2 to UEFI Dell 7060 Machines

August 1, 2018, 8:07 am

≫ Next: Problem getting a linux PXE network boot to start like the windows one

≪ Previous: RU7 Upgrade Fails

$

0

0

I need a solution

Hello all,

Company recently recieved a bunch of Dell 7060 machines, however I have no idea how to imagine UEFI machines. I would like some technical guide please.

0

---

Problem getting a linux PXE network boot to start like the windows one

August 1, 2018, 9:31 am

≫ Next: Trouble Installing Tools 3.2

≪ Previous: How to setup Ghost Solution 3.2 to UEFI Dell 7060 Machines

$

0

0

I need a solution

Hi all

running into a problem with creating a linux PXE network boot to work like the windows one i created. With the windows one in the startup file i have it going to the network share m: then the folder cd ghost and starting up a bat file that starts the ghost server session and the ghost application to copy an image from the server and bring it down to the unit. It works fine with windows but i am not sure how to make it do the same thing for a system i want to copy the linux image from/restore a linux image to. i am guessing the problem lies with the rc.startup file if anyone can help point me to how to do this or if you can let me know an easy way to get this done it would be a big help. Thanks.

0

Trouble Installing Tools 3.2

August 7, 2018, 9:51 pm

≫ Next: Restoring MBR and EFI Images with the same Ghost USB

≪ Previous: Problem getting a linux PXE network boot to start like the windows one

$

0

0

I need a solution

Hello Anybody.

Just checking in with any of you, Has anyone experienced installation problems with Ghost Solution Suite 3.2 on a windows 10 machine? I have tried installation on multiple Windows 10 Machines but I still can't use the Boot Disk Creator with an App Error. All I am trying to do is crate a Windows 10 Ghost Image and then Ghost another 9 Machines. Does that make sense? Please advise. Anybody? 

0

Restoring MBR and EFI Images with the same Ghost USB

August 8, 2018, 7:54 am

≫ Next: Deploy Anywhere fails after image deployment - Help!

≪ Previous: Trouble Installing Tools 3.2

$

0

0

I need a solution

I am attempting to find an automated solution to configure ghost to NOT convert images at all. I recently upgraded to GSS 3x and everything is working really well. The only problem is I am now restoring MBR and EFI images to different hardware.

This is my current script that kicks off ghost in WinPE

ghost64.exe -szee -fdsp -clone,mode=restore,src=@MCusb,dst=1 -sure

I attempted to add -noconvert to the script as mentioned in this support article. However i get a pop-up stating that the switch is not recognized. The article suggests it should work in GSS 3x, but I know its an older switch.

The old images restore fine because they are booting to Legacy BIOS anyways. The new devices work as well because the capture is EFI and the system is only EFI so ghost does not attempt to convert. However I have one device that uses Legacy, but it still has UEFI boot capabilities and that messes things up if I don't specifically Boot to the Ghost disk in Legacy mode (Non-EFI). But I would prefer not have to press F9 on every device as it boots.

Thanks in advance for any advice!

0

Deploy Anywhere fails after image deployment - Help!

August 8, 2018, 8:24 am

≫ Next: Altiris eXpress Server Service Fails to Start

≪ Previous: Restoring MBR and EFI Images with the same Ghost USB

$

0

0

I need a solution

Hello! So I'm trying to get DeployAnywhere to inject drivers after deploying an image on a new PC but for some reason it isn't loading. Checking the logs it says it cannot be retargted to run on the computer, which indicates it is using the wrong path to windows but it is the correct path. Starting up the same computer after imaging with a ghost boot disk I am able to run the same command with deploy anywhere and it works fine. Any ideas? Below is the full log:

********************* Starting of Retargeting *********************

Mon Aug 06 21:03:44 2018

Start of Main().

Command line :  DeployAnywhere64.exe /target=c:\Windows /ddb=M:\driversdb /handleNonCriticalDrivers=minisetup

Symantec Ghost 12.0.0 (build=10517).Built on Mar 17 2017 16:04:40 Copyright (C) 2017 Symantec Corporation. All rights reserved.

Start of DeployAnywhereMain().

Start of Initialize().

Computer Bios information

	Parameter Name		Parameter Value

	--------------		---------------

	Manufacturer  		LENOVO

	Product Name  		2518C3U

	Version Number		ThinkPad T410

	Serial Number		R85K6R1

	UUID          		81ce3dda-3a50-cb11-8d09-d7bcffa8c89c

	M&P combined  		LENOVO 2518C3U

Error: Unable to create the retarget system object. The system volume specified cannot be retargeted to run on this computer. 

End of DeployAnywhereMain().

DA Return code is 3(GH_ERROR).

********************* End of Retargeting *********************

End of Main().

0

Altiris eXpress Server Service Fails to Start

August 9, 2018, 4:55 pm

≫ Next: Access Denied to most commands in console

≪ Previous: Deploy Anywhere fails after image deployment - Help!

$

0

0

I need a solution

I recently installed RU7 on three Ghost Consoles and now when I restart the server the Altiris eXpress Server Service fails to start.  Checking the Windows Event Viewer I see the following events immediately following a restart (paraphrased):

1. Warning, "Registry key NtfsDisable8dot3NameCreation it not 0."
2. Information, "Working directory set to: C:\Ghost"
3. Information, "Licensed for: xxxxxx nodes Symantec GSS"
4. Error, "Error 10065 joining multicast group on adapter 0"
5. Error, "Error initializing Symantec Ghost Solution Suite components"
6. Information, "AxEngine is shutting down"

When I check the Services MMC I see that the Altiris eXpress Server service is set to start Automatically but is NOT started.  If I manually start the service it does start.  Checking Event Viewer after the manual service start I receive the following events from the list above: 1, 2, 3.  Then I receive the following:

1. Information, "Brokering Engine initialized"

A collegue was experiencing this issue on fresh Windows installation with Ghost 3.2 and the RU7 update.  I updated a Ghost 3.2 RU6 machine to RU7, performed a restart, and am seeing the same error on the updated machine.

Any advice would be greatly appreciated.

0