Ghost Console Won’t Run Remote Batch File

I need a solution

We have been doing a two-Task process to deploy a piece of software to computers using Ghost Console 11.5.1.2266:

Task 1) Deploy an installer and batch file to a specified directory on the target machine(s).

Task 2) Run the batch file in the deployment directory on the target machine, which successfully installs the program.

I tried this with a new piece of software, and while Task 1 copies the installer and batch file into the directory successfully, Task 2 does nothing other than claim to have completed successfully. When I run the deployed batch file on the target machine it works properly, just not through the Ghost Console Task. I tried this on multiple machines with the same results.

When I run the batch file on the target machine I can see Windows Command Processor open in Task Manager, which does not happen when I run the Task through Ghost. I do see the Ghost System Tray Provider open while the warning window comes up, but then it closes and nothing else happens.

I took the successful Task 2 for the first piece of software and changed the target information to match the new program, and it still did nothing. Then I changed it back to the original target and it worked properly for that software.

Any ideas?

0

Related:

Windows Store and Sideload apps don’t work after reboot when User Layers enabled

Identify any prerequisite AppX packages that are installed by your App installer. For instance, look for commands like this in the installer PowerShell script:

Add-AppxPackage -Path <something>

Or if your installer package contains a Dependencies folder, it may be sufficient to inspect the contents of that folder. There is no simple, clear path to determining the specific AppX packages that are included as prerequisites, so you may need to do some investigation to determine them.

Your list might look like this, for instance:

Microsoft.NET.CoreRuntime.1.1.appx

Microsoft.VCLibs.x64.14.00.appx

Microsoft.VCLibs.x86.14.00.appx

Once you have a list of dependent AppX packages, you need to repair/reinstall some or all of them after each reboot. Manually test this command for each package to determine which need to be fixed:

Get-AppXPackage *Microsoft.NET.CoreRuntime.1.1* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}

Now that you have the commands you need to run to fix your App, you can build this as a CMD file that a user has to run manually, or as some manner of login script. For instance, you could just put a BAT file in c:programdatamicrosoftwindowsstart menustartup that would run on each user’s login.

Batchfile:

@echo off

start /min powershell.exe “c:fix.ps1

fix.ps1:

Get-AppXPackage *Microsoft.VCLibs* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}

Get-AppXPackage *Microsoft.NET.CoreRuntime.1.1* | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)AppXManifest.xml”}

(Note the * chracters which do wildcard matching to allow you flexibility. The line for Microsoft.VCLibs, for instance, captures both the x64 and x86 packages.)

Related:

VMAX3: Command rejects for erease command (11)

Article Number: 502444 Article Version: 3 Article Type: Break Fix



VMAX3 Series

IOS000I 7514,C3,CMD,11,0E00,,01450000,SMS1E2,EMCSCF81, 699 8000000014FFFF0200000000000000140902202D02050F02000000E000014500 System found a permanent I/O error in device error recovery CMD Command reject

Error code 1115.11

Error code 1122.D1

The Ficon is incorrectly doing a unit check sense of command reject for certain command 11 erase commands

A fix is being generated for this issue.

Related:

Starting GSS jobs from command line

I need a solution

Hi – I have GSS 3.2 RU7 installed on 2012R2.  I would like to be able to set off GSS jobs via the command line (.BAT files) on this system.

For example, I want “Job 92” to run on machine “PC01”.  Is there a way to do this?

I know the drag and drop is very easy, but I am looking to automate as much as I can, e.g., avoid having to log in to the console to set off a job.

0

1538049335

Related:

Avamar Client: File System backups fail with (code 53: The network path was not found)

Article Number: 499514 Article Version: 3 Article Type: Break Fix



Avamar Client,Avamar Plug-in

File System Backup logs will show the following entries:

2017-04-19 07:04:36 avtar Error <5137>: Unable to open “C:UsersAdministratorDesktop! Don’t delete me! I’m helping Cybereason hunt for ransomware!c1ZUCyAe.jpg” for backup (code 53: The network path was not found).

2017-04-19 07:05:04 avtar Error <5137>: Unable to open “C:UsersAdministratorDesktop! Don’t delete me! I’m helping Cybereason hunt for ransomware!c2mwh.xls” for backup (code 53: The network path was not found).

2017-04-19 07:05:32 avtar Error <5137>: Unable to open “C:UsersAdministratorDesktop! Don’t delete me! I’m helping Cybereason hunt for ransomware!c2RL73yy.xls” for backup (code 53: The network path was not found).

Cybereason generates random files with common end-user type file extensions (.jpg, .xls, .mp3, etc.) and distributes them throughout User profile and other folders to assist with detecting and preventing Ransomware attacks. These files cannot be accessed by design and generate the following entries in File System backup logs.

Cybereason software introduced to environment

A common attribute of these files is they are hidden (-h attribute). Use the –nobackuphidden flag to exclude these files. Add it to local avtar.cmd or to the dataset.

Any files with the -h hidden attribute will be excluded.

Related:

XA7.15 – Citrix Config Sync Service failed an import

Solution1:

Make sure you don’t have any orphaned SID’s in any of your Published Applications/Desktops. You can use this small PowerShell script to determine the affected resources..

Run the below powershell cmd to see which application / desktop has the SID associated.

$PublishedApps = Get-BrokerApplication | where {$_.AssociatedUserNames -like “S-1*”}

Foreach ($App in $PublishedApps)

{

Write-Host ” _” $app.Name “is broken”

}

Solution 2:

Disable and Enable Localhostcache by running the ps cmd:

To disable Local Host Cache (and enable connection leasing), enter:

Set-BrokerSite -LocalHostCacheEnabled $false -ConnectionLeasingEnabled $true

To enable Local Host Cache, enter:

Set-BrokerSite -LocalHostCacheEnabled $true -ConnectionLeasingEnabled $false

Solution 3:

To recreate LHC

> Open PowerShell on one of the DDC and enable Local Host Cache by executing following commands

asnp Citrix*

> Download PsExec tool from https://docs.microsoft.com/en-us/sysinternals/downloads/psexec and unzip one of the DDC machine

> Get a command prompt running as Network Service using the command: PsExec.exe -i -u “nt authoritynetwork service” cmd.exe. In that command prompt, navigate to the directory C:Program FilesMicrosoft SQL Server120ToolsBinn

> Stop the Citrix High Availability Service

> Execute: “SqlLocalDB.exe stop CitrixHA”

> Execute: “SqlLocalDB.exe delete CitrixHA”

> Delete the files HADatabaseName.* and HAImportDatabase.* from C:windowsServiceProfilesNetworkService.

> Start the Citrix High Availability Service.

Related:

How to recreate Local Host Cache on XenApp/XenDesktop 7.12 or later

Recreate LHC on the Delivery Controller by the following steps:

1. Download PsExec on the Delivery Controller

PsExec – Windows Sysinternals

https://docs.microsoft.com/en-us/sysinternals/downloads/psexec

2. Stop Citrix High Availability Service

3. Run PsExec on Command Prompt and switch to Network Service account

> psexec -i -u “NT AUTHORITYNETWORK SERVICE” cmd

> whoami

nt authoritynetwork service

4. Move to the path with SqlLocalDB

> cd “C:Program FilesMicrosoft SQL Server120ToolsBinn”

5. Stop/delete CitrixHA (LocalDB)

> SqlLocalDB stop CitrixHA

> SqlLocalDB delete CitrixHA

6. Remove the related files below in C:WindowsServiceProfilesNetworkService

– HADatabaseName.*

HAImportDatabaseName.*

7. Start Citrix High Availability Service

8. Confirm that CitrixHA is recreated

> SqlLocalDB i

CitrixHA <<<< disappears just after stop/delete in step 5, and appears after start Citrix High Availability Service in step 7

MSSQLLocalDB

Related:

Windows 10 Enterprise 1803 Altiris PM Import Patch appears broken

I need a solution

Hi,

I downloaded the Windows 10 Enterprise Aniversarry Edition 1803 patch via PM Import. Both the ISO and the Bat file came down but the bat file does not appear to execute the ISO patch. When I compared the code in the Bat file from the prior 1703 patch that came down via PM Import the code in the bat file was drastically different.

This leads me to belive that the code in the bat file that is part of the patch is broken. Below is the code in the bat file for the new 1803 patch.

Is this bat file in the patch broken or am I missing something here?

undefined
0

Related:

Endpoint Agent 15.1 Deployment via AD

I need a solution

Hi, everyone.

As per title, I would like to deploy Endpoint Agents for DLP 15.1 via AD.

I have read this article: https://www.symantec.com/connect/articles/deploy-d…

However, what I don’t understand is that the article did not mention anything regarding the pem files as the agent packages that I have generated contains these following files as shown in the file attached in this post.

So I understand that the msi file can be transformed into mst with the parameters from the install batch file but how do I include the pem files and deploy them via AD?

Thanks in advance.

0

Related:

How to Build an Evict Script

The script should be built from a working DDC.

Summary

Generating Evict Script:

  1. Obtain the SID of the failed DDC.
  2. Get the database schemas for the site version.
  3. Configure the right command parameters to obtain the script.
  4. Build the PoSH script to generate the SQL script.

Launch a PowerShell prompt and add Citrix modules (asnp Citrix*).

1. Obtain the SID of the failed DDC

To obtain the failed DDC SID on the database, run the following command:

Get-BrokerController

It should return the list of controllers for the site and the state of each one of them.

It’s important to run this command to obtain the controller SID because we need the SID registered on the db, not the one on AD since it might be slightly different if the account has been removed and recreated, or changed the SID in any other way.

User-added image

Notice that the failed Controller State is “OFF”.

2. Get the database schemas for the site version

In order to know which database schemas do you need to clean on the database, run the following command:

Get-Command Get*DBSchema

For 7.16 it will return:

User-added image

Open a PowerShell ISE as an administrator and paste all the commands.

3. Configuring the right command parameters to obtain the script

For each DBSchema command, you can configure the same parameters, meaning that the syntax will work for all of them.

According to the latest PoSH SDK documentation available, the minimum required parameters to build an Evict script are:

  • DatabaseName: Meaning the site database
  • ScriptType: We will use “Evict”, however, we can generate Login or full database scripts.
  • SID: SID stored on the database for the controller that we want to evict.

So the parameters for each service DBSchema should look like:

Get-LogDBSchema –DatabaseName “MySiteDB” –ScriptType Evict –SID “Controller to evict SID”

Also for Monitor and Logging schema, you can remove the data on the Site DataStore by using the following commands:

Get-LogDBSchema -DataStore Site –DatabaseName “MySiteDB” –ScriptType Evict –SID “Controller to evict SID”

Get-MonitorDBSchema -DataStore Site -DatabaseName “MySiteDB” –ScriptType Evict –SID “Controller to evict SID”

4. Building the PoSH script to generate the SQL script

  1. Open a PowerShell ISE and open the script view.
  2. Add Citrix SnapIns and paste all the “get” commands obtained earlier alongside the parameter string build in the step before.
  3. Define two variables, one for the database name and the other one for the non-working SID.
  4. We will also need to add a function to write the content to a file. There are several ways to do it, but I’ll be using Out-File “filepathname” –Append

So the script should look like:

User-added image

Once you run it, go to the path and you will find the Evict.sql file generated which is a SQL script that can be run either on the SQLCMD or the Management Studio in SQLCMD mode.

Related: