Horizon 7.2
Profiles are discarded by setting the HKLM\Software\Microsoft\Windows 
NT\CurrentVersion\ProfileList\{SID}\State value to 128 at logoff, which means 
the OS thinks that it is a temporary profile and purges it. So nothing from 
C:\Users or HKCU is retained at all. Yet still – next logon is half the time.
We’re not using Persona Management of any sort, and I’ve removed all logon 
scripts
The testing I am doing isn’t doing a refresh or recompose on reboot, which is 
why I’m getting really confused. I thought about Superfetch, which has been 
disabled by the VMware OSOT, but re-enabling that didn’t do anything.

Well confused!

From: [email protected] [mailto:[email protected]] On 
Behalf Of Jack Kramer
Sent: 06 February 2018 15:35
To: <[email protected]> <[email protected]>
Subject: Re: [NTSysADM] Hmmm....

What version of Horizon are you running? You say profiles are discarded—are you 
redirecting profiles to disposable disks or retaining them on the C: drive? Do 
you have the registry keys set to discard profiles as well as the Horizon 
settings for it? (The ones I can think of offhand: removing local/roaming 
profiles at logoff under the normal Windows administrative templates; the 
Horizon Persona Management ADM/ADMX template settings; the Horizon disposable 
disk settings)

If you’re just using redirection to disposable disks and not also discarding 
the profiles the other ways I would expect there’s some data being kept in HKLM 
that wouldn’t need to be recreated at every subsequent login. HKCU would be 
thrown away with the disposable disk (since it’s the user hive) but anything in 
HKLM would be retained until the refresh operation occurs on reboot. Also, if 
you’re perhaps triggering a login script that licenses some software on a 
per-user basis, etc.
----
Jack Kramer, Senior Consultant
Small Type Computing - www.smalltype.net<http://www.smalltype.net>
W: 855-765-8973 x101 - C: 248-635-4955


On Feb 6, 2018, at 9:50 AM, James Rankin 
<[email protected]<mailto:[email protected]>> wrote:

Ok, so can anyone shed any light on this….

I have a VMware VDI implementation running Windows 7. The user profiles are 
discarded at logoff, so no user profile information is retained at all on the 
machines. When a user logs off, the machine is restarted. This keeps all 
machines in the pool in a pristine state (as the client wants).

However, when a user logs on for the first time, the logon takes 20 seconds. If 
I remove the machine from the pool (so it doesn’t get restarted at logoff), and 
log the same user in again (bear in mind the profile is discarded at logoff), 
the logon takes 10 seconds. Each subsequent logon for the user will be solidly 
10 seconds, unless I restart the machine, and then we are back to 20 seconds 
for the first logon.

It doesn’t matter if I log a *different* user in before logging in the test 
user – each user experiences their first logon to the machine as 20 seconds, 
and all subsequent tries as 10. Each user has their profile discarded at 
logoff. It’s almost as if some process is running at first logon that then 
stores some user-specific information or data outside of the user profile but 
in a user-specific location – yet I can’t for the life of me speculate as to 
what it might be.

Any ideas anyone? 😊

Cheers,



<image001.png>

<image006.jpg>

<image007.jpg>


James Rankin CTP ACA vExpert
Technical Evangelist / Media Hound
Howell Technology Group
Office: 0191 4813446
Mobile: 07809668579
Email: [email protected]<mailto:[email protected]>

www.htguk.com<http://www.htguk.com/> | Twitter<https://twitter.com/htguk> | 
Linkedin<https://www.linkedin.com/in/megan-holland-368bb0150/> | 
Facebook<https://www.facebook.com/HTGUK>

COMPANY INFORMATION
Howell Technology Group Ltd is a limited company registered in England with 
registered number 5520670 and VAT registered number GB862 6660 04. Our 
registered office is at 2.30 One Trinity Green, Eldon Street, South Shields, 
Tyne & Wear, NE33 1SA

CONFIDENTIALITY NOTICE
This message is intended solely for the addressee and may contain confidential 
information. If you have received this message in error, please send it back to 
us, and immediately and permanently delete it. Do not use, copy or disclose the 
information contained in this message or in any attachment.

PRIVACY POLICY
For information about how we process data and monitor communications please see 
our Privacy Policy.


Reply via email to