[THIN] Re: Show Clock on XenApp 4.5/Server 2003
In most cases yes, but in this case, the stuckrects2 key (or rather the settings value below it) contains various settings within a single binary value - i.e. the task-bar placement, clock etc...
Using the change user method would capture the whole value, not just the bit which controls the clock I believe...
I guess the key to doing this properly would be to have a script read the value, patch the appropriate bit and then write it back...
However, unless there are other major changes, there would be no harm in capturing the whole value and using the method described by Jim - to be honest, this should work just fine... 

Regards,
Jon

---


On Sep 21, 2008, at 10:08 AM, Jim Kenzig http://thin.ms wrote:
It only changes the settings you change while in install mode, doesn't it? 
Jim Kenzig
Blog: http://www.techblink.com
On Thu, Sep 18, 2008 at 8:16 PM, Joe Shonk <joe.shonk@xxxxxxxxx> wrote: That would change the whole Stuckrecs2 key and not just the one bit he wants to toggle. 


Joe
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Jim Kenzig http://thin.ms 
Sent: Thursday, September 18, 2008 4:36 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Show Clock on XenApp 4.5/Server 2003
Yes and that is easily done via the patented kenzig CUI trick. Going to a command prompt, running change user /install make your changes to add the clock. Then do a change user /execute from the command prompt. 

Jim Kenzig
Blog: http://www.techblink.com
On Thu, Sep 18, 2008 at 6:54 PM, Steve Snyder <kwajalein@xxxxxxxxx> wrote:
I just set it in the mandantory profile, or one should be able to set it in the default profile if one is not using mandantory profiles
On Fri, Sep 19, 2008 at 10:34 AM, Jeremy Saunders <Jeremy.Saunders@xxxxxxxxxxxxxx > wrote: 

Hi Adam,
I've been using that script and method on all deployments for years, and it works a treat.
However, you need to understand that it won't change for the first login, or after you have deleted their profile….only on the second login. This is because the explorer.exe shell has already started, and initialized itself, so the registry changes will have no effect until the next time it starts. It's extremely difficult to get in and do stuff before explorer.exe initializes. You can test this by killing the explorer.exe process and starting a new one. 


Cheers,

Jeremy.
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Adam Rosenberger 
Sent: Thursday, 18 September 2008 10:41 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Show Clock on XenApp 4.5/Server 2003


I am beyond frustrated now.
I have been trying for 3 days now to show the clock for a published desktop. In my GPO, I have made sure to disable the choices to hide the clock and hide notification area (systray).
I have tried various reg hacks, to no avail. I finally stumbled upon an old posting from Jeff Durbin on 2003 in which he posted a script file which is then referenced by usrlogon.cmd. This still failed to work.
After further research another posting from Jeremy Saunders in 2007 referenced adding the following to the usrlogon.cmd: 


cscript "%systemroot%\system32\SetTaskBarOptions.vbs" //Nologo


This has also failed to work.


Can anyone please advise?




Adam Rosenberger

RSK-SImon, LLC

Director of Information Systems

arosenberger@xxxxxxxxxxxxxxxxxxx

704-774-4025
This communication,along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this transmission in error, please delete it from your system without copying, distributing,printing or saving it or its attachments in any manner, and notify the sender of the error by reply e-mail or by calling 704-372-7892. This communication does not form any contractual obligation on behalf of the sender or RSL- Simon, LLC and its subsidiaries. 

Confidentiality and Privilege Notice
This document is intended solely for the named addressee. The information contained in the pages is confidential and contains legally privileged information. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone, and you should destroy this message and kindly notify the sender by reply email. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you.

Other related posts: