Ghost Solution Suite

We were Ghost 2.5 users, and in that version there was a way to allow users to right click the systray icon and launch reimage tasks assigned to their computer.  Apparently that's not a thing now.  But we need a way for users to perform their own tasks, so it seems the best option would be as follows:

Delegate each user permission to their own Folder on the Ghost Console

Install Ghost Console on user's "production" pc

Then they can use the console on their production pc to re-image their test PCs.

Unless there is another way to do it, that I haven't found yet.  If so, please let me know.

The problem though is that I can't figure out how to install the remote console, per this article:

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

It apparently doesn't work to install it remotely to a "client" PC (Which is ridiculous to put in the article, how about you fix that).

So, how do I get a remote console installed on a Windows 10 PC and connected to the GSS 3.2 server?  Just running axinstall and pointing it to the share via unc didn't seem to work.

Any advice?

N/A - Removed as duplicate comment

GSS 3.2 does not have the capability for clients machines to kick off jobs. You could use remote consoles to do this functioniality as shown in the kb you referenced above.

The instructions you list above are spot on and yes you can install the remote console on windows 10 (see support matrix).

The issue I have seen is after installation the remote console will not connect to the server share properly, maybe a database connection error? You need to create a ODBC connection on the client machine that points to the SQL express server on the Ghost Solution Suite server.

I've been trying to get the remote console to install and thus far I have failed installing it in the following ways:

Remotely from the existing Console System to Windows 10, Windows 2012R2 & Windows 2016

Locally on a Windows 10 pointing to the existing share.

Are we sure that it works?  Have you tried it by chance?

Corey

Additonally, if you can do the remote install to Windows 10, then why does the article say in bold:

This is only able to be done remotely with server class operating systems. Testing has shown this will not work with client class operating systems.

Quick update, I got the install to work on Server 2012R2 pushed forom the console server.

I installed the dagent, modifed the "file server path" to be the UNC during install, and I had pre-installed .net 3.5.

Not sure which one was the answer though.

Now I just need it to get to windows 10

Maybe those helped?

C-dog,

That kb was written before support for windows 10 was announced as a viable OS for GSS console installs. I have updated that document to reflect the currently supported operating systems. This will take a few hours before changes show on the website.

Windows 10 install should function similarily, I have seen and helped install in Windows 10 OS multiple times.

OK, so I have an additional console installed.  I was unable to perform the remote install to Windows 10 from the GSS Server(2012r2) to 3 different Windows 10 PCs though.

But copying the DSSetup folder to the local machine and running setup locally did work.  We can work with this.

Thanks.

Corey

Corey,

Installing locally using the axinstall.exe is the best way to do this. The remote installer can be spotty when it comes to firewall ports, connectivity etc.. and tends to not be as reliable as the manual option.

Please mark the most relevant answer as a solution if your issue is resolved.