AppVol 2.10 Slow logon time. "Error from Manager (error code 401): NTML Authentication Invalid: Authentication failed for user:"

[Piear]

"Error from Manager (error code 401): NTML Authentication Invalid: Authentication failed for user:"

We are experiencing long logon time with user assigned Appstacks.

When users log on to VDI desktops the Appstacks are not mounting after logging into the OS (Windows 7 ENT). :smileyconfused:

After exploring the forum, guess I'm not the only one.

Did anyone make any movement on this?

Piear

[epa80]

As of now the "workaround" to get rid of the NTLM error, is the DEMO=1 fix that's mentioned in another thread. We had tried other fixes such as correcting our WINS addressing, patching Microsoft critical patches, and none were long term fixes. We still got the 401 error randomly until we did the DEMO fix.

Regarding slow logins: we've seen over the last 2 weeks our login times jump to over a minute when stacking 2 app stacks. We have a case open with VMware, but, as of this writing, we have no idea what is causing it. We're on vSpehere 6U1, App Volumes 2.10.

[Piear]

epa80‌,

We also attempted the work around to configure svmanager_server.bat to demo mode.

The demo mode change on the app volumes servers did suppress the NTLM messages within the environment but we are still experiencing long log on times and inconsistent app stack attachments.

However what exactly is Demo mode? I am very hesitant  to implement a demo system into production without knowing what the details are.

We are still working with support on this case.

Thanks epa80‌ for your feedback.

[epa80]

Piear,

This was provided to me by VMware support when I asked what exactly DEMO mode is when enabled.

Per your questions regarding what impact changing the config file will have when setting demo=1. This will add a static image on the dashboard for the information displayed.  This does not disable NTLM it only does not enforce NTLM on computer startup. Meaning if NTLM fails App Volumes Agent will still communicate direct with the App Volumes Manager on computer startup.  These are the only two changes.  This is the current supported work around by engineering.

[Piear]

Thanks epa80‌!

This is a great starting point. I will provide an update as well once we have an update from vmware.

[Jason_Marshall]

It is not a mode the MAnager is placed in but a porly named variable that disables NTLM enforcment. It is harmless and the next version with remove the static data and give it a nicer name. Functionality does not change though. demo=1 is safe.

[Maarten_Caus]

Hi,

I came across the error and I want to try the setting Demo=1.

Can you point me to the right post because I can t find it  .

Kind regards,

Maarten

[Raymond_W]

Hi Maarten,

Change this line in c:\program files (x86)\clouvolumes\manager\svmanager_server.bat:

From: set DEMO=

To: set DEMO=1

If the demo=1 is set, you will see fake data in the App Volumes console.

[Piear]

Thanks Raymond_W‌ for  your input and helping maarten‌ out.

maarten‌, as just an FYI before you make any configurations changes in your environment contact VMware Support for their blessings.

NOT ALL ENVIRONMENTS ARE THE SAME.

[Piear]

Hello All,

With the assistance of vmware support and weeks of testing, we were able to narrow it down to our NTP settings on our ESXI hosts.

The time on some of our ESXI hosts were out out of sync within the environment. Once we set the correct time and have all the ESXI hosts synced to the SAME and viable NTP server,apps stacks were mounting on a consistent basis. We also got out of demo mode.

[cyberfed2727]

FWIW this topic is actually discussed in the 2.11 users guide. Not sure if it applies to 2.10 but worth a shot..

Disable NTLM Authentication

NTLM authentication is used to verify the user, computer, and the domain of the agent when it makes

HTTP requests to the App Volumes Manager.

You can allow or stop the HTTP request from proceeding by defining a system environment variable.

Procedure

1 On the App Volumes Manager machine, open Windows Explorer.

2 Right-click My Computer.

3 Click Properties > Advanced System Settings > Environment Variables.

4 In the System Variables panel, click New.

The New System Variable window appears.

5 Enter AVM_NTLM_DISABLED in the Variable name text box.

6 Enter 1 in the Variable value text box.

7 Restart the App Volumes Manager service.

This disables the NTLM authentication.

[hockeyguyin714]

Disable NTLM only applies to Computer logins on computer startup.   This would still fail for authentication for the user.

The difference is easily seen users are domain\username  computers are domain\computername$