Forum Replies Created
-
Posts
-
Hi,
Cheers for the heads up – Here’s the situation:
– The new Wyse build doesn’t have users as being administrators for the changes to be preserved due to the changes in the write filter as long as the directories are excluded – great fature!
– our users want to be able to change their desktop settings such as display resolution, accessibility options just like they can on their normal XP desktops
– i’ve tried excluding just down to documents and settings without the windows directory but the changes to the display settings weren’t being saved
– i’m not sure where you’re coming from in regards to trogans and viruses – the users aren’t admins, we run an extreemly locked down environment where they can’t load anything and it auto-connects as needed. The only case where i’d see this coming into effect is if there was a trojan on the network that was remotely exploiting these systems – is that where you’re coming from? And if so, hows this any different from normal XP?
– I am interested in the impact on the life of the units – is there any info about this I can review?If there is another way to allow users to save their settings such as registry changes without needing to log them off, log on as administrator, disable the write filter, reboot, make the change, re-enable the write filter then i’m open for it.
I’ll be looking at locking down the exact changes being made from the generalistic folder based restrictions i’ve talked about above (to get it to work) to being the exact files as needed. If you can provide some info – that’d be great.
Hi All,
Managed to find the solution – quick eh!
Exclude c:Documents and SettingsUser or just C:Documents and Settings
Exclude C:WindowsSystem32configAll good!
I always run mstsc with a specific rdp session but you should be able to do this by editing the default.rdp for the user.
Add in the following line
displayconnectionbar:i:0
The connection bar will briefly show and then go away.
Hope this helps
Hi all,
Very happy to say that the V90LE imaging is now working with the Onboard EHCI disabled – wohoo!
The very annoying thing is that BIOS pushing is now disabled – I read that was because it could leave the unit unbootable. This worked fine in the previous version in my experience – is there a risk in re-enabling it?
Also, I tried the usb 2 for DOS bit and when the rem bit in the relevant line in the config.sys was removed it was failing to find a usable command.com – can you please post your working config.sys / autoexec.bat versions so that we can try this! Pleaeease.
Kieran
Do you have some folder exclusions configured for your C:Documents and Settings folders?
HI all – I found a fix for this.
On the RDP destination, do the following
– Start regedit
– Edit the following key – HKLMSystemCurrentControlSetControlTerminal ServerWinStationsRDP-TCP
– Set the fInheritAutoLogon as false – i.e. 0
– Set the fPromptForPassword as true – i.e. 1
– Set the domain as applicableMade my life a lot easier – hope it helps others!
Here’s the gotcha – if you take the “user” out of administrators, they wont be able to use any custom scripts you’ve got to write changes to the device when the write filter is enabled.
Case in point – i did just that and took user out of administrators. We run our devices with the write filter enabled but due to the way that the ewf works, you can’t write changes unless you’re an admin.
If this isn’t an issue or you’ve got write filter disabled, then you should be fine.
Just found this – http://blogs.msterminalservices.org/conger/2006/11/28/microsoft-releases-terminal-services-client-60-for-windows-xp-and-windows-server-2003/
gnnnnnarg!
Anyone had any luck making this work?
