Ghost Solution Suite

 View Only
  • 1.  Client passwords not matching what is set in the console.

    Posted Jul 07, 2016 03:14 AM

    Having a strange problem where when we set a password in the colsole (production agent settings > password protect admin properties from user) and password I set doesn't work on the client.

    I've tried something as simple as the letter "a".  I can remove the password in the console and it's gone from the client right away.  Then set it back... and it has a password... just not what I typed. 

    We have just moved to a new server.  Old server was GSS 3.1 - SQL 2008 - Windows Server 2008r2, new server is GSS 3.1 - SQL 2014 (Windows Server 2008r2).  I exported the old eXpress database from SQL 2008, imported to the new server in SQL2014 and then installed GSS 3.1.  No problems, everything seemed to come across fine.

    The server has a different name and IP address to the OLD server.  Clients are all Windows 8.1.

    I've tried removing the client from the console and having default client settings with the password.  I've tried removing the console and having no default client setting then adding it later.

    It doesn't matter what I do the password I type in the colsole doesn't seem to translate corretly to the client.

     

    Is there anything that stands out that would be causing this issue?



  • 2.  RE: Client passwords not matching what is set in the console.

    Posted Jul 09, 2016 10:38 AM

    We didn't bother reporting it but we are facing the same problem, it was there from the beginning (the original non-patched GSS 3.1)

    We decided to bypass password usage for the time being, and sadly we will probably have to disable the altiris DAgent tray icon to prevent any access, since we're using it in a school campus.



  • 3.  RE: Client passwords not matching what is set in the console.

    Posted Jul 18, 2016 02:46 AM

    I have no idea how you might set this, but could it be an ASCII/UNICODE issue, or an encryption issue ?



  • 4.  RE: Client passwords not matching what is set in the console.

    Posted Jul 20, 2016 07:20 PM

    Still not fixed here. I not sure where I can change encryption settings like that. We don't have encryption turned on in any of our clients.  I've try deleting the express database and starting a fresh database.  Same problem. 



  • 5.  RE: Client passwords not matching what is set in the console.

    Posted Jul 29, 2016 05:20 AM

    Hi, the same problem here. Change code page not resolve issue. Anyone find fix path ?



  • 6.  RE: Client passwords not matching what is set in the console.

    Posted Jul 29, 2016 05:52 AM

    I have installed the last version :o(



  • 7.  RE: Client passwords not matching what is set in the console.

    Posted Jul 29, 2016 06:25 AM

    Hi all,

    This is in the "known issues" section of the release notes for 3.1 MP2. I've been seeing the issue for a lot longer though but I don't think they've picked it up 'til now.

    https://symwisedownload.symantec.com//resources/sites/SYMWISE/content/live/DOCUMENTATION/9000/DOC9335/en_US/Ghost_Solution_Suite3_1_MP2_ReleaseNotes.pdf?__gda__=1469928584_569c3cdf22c14ef52eae4eb91bafbccc

     

    The article it links to says a fix has been released https://support.symantec.com/en_US/article.TECH234826.html

    I certainly can't find it though....



  • 8.  RE: Client passwords not matching what is set in the console.

    Posted Aug 11, 2016 03:30 AM

    Should fixed in GSS 3.1 MP3

    "Invalid Password error is displayed on the client computer when you access the DAgent TECH234826 properties if the password is set from the Ghost Solution Suite Console."

     



  • 9.  RE: Client passwords not matching what is set in the console.

    Posted Aug 12, 2016 04:42 AM

    Hi there. I install new Maintence Pack 3.After Install nothing change, with this problem. I think maybe i doing anything wrong (



  • 10.  RE: Client passwords not matching what is set in the console.

    Posted Aug 12, 2016 07:38 AM

    After applying MP3, update the Dagent to Version 6.9.2205 and set a new password for the DAgent Settings it work for us.