We've used what appears to be this method for a good while, but with one variation..
The local workstation has an environment variable %WSDIRALL% which points to the location, and the GPO just points to %WSDIRALL%
We did it this way because our environment has multiple "controlled" desktops with different applications in each room.
Oddly enough, our IT dept balked slightly at the thought of having hundreds of GPOs so doing it this way kept us in their good grace.. And it's child's play to update the environment variable locally/remotely.
This does of course mean we have multiple desktops/start menus, but it reduces the HD calls of "I'm trying to run appx in room123 and it isn't working" (when appx isn't in room123)
The only slight drawbacks:
1. Some MSIs appear to HATE having the common desktop/start menu redirected, so if we're deploying anything I tend to add a couple of lines of code which temporarily puts it back to "factory default"
2. You need a GPO which gets applied to non-locked down PCs which puts the common start menu/desktops back to normal otherwise moving a PC out of the locked-down GPO would still leave it with the registry changed to the locked down state. If you're doing this with 7, then you need 2 since 7's normal start menu/desktops are in a different location.
This may be the mickey-mouse method we used as I'm talking about the MACHINE level (all users) start menu/desktop.. And our method is straight-out reg hacks since the days of NT4
Originally Posted by TheScarfedOne what you could do is call a vbs script which displays a message box with a timeout in it Yep, that's exactly what I do - only with AutoIt instead of VB as I prefer using AutoIt
The only problem I had was that on XP, running as a scheduled task, you were not guaranteed to see the message screen pop up because of (I believe) the restrictions applied to Task Scheduler.
I ended up running psexec included in the same folder as my AU3. The AU3 then calls PSEXEC which would then interact with the desktop..
A complete dog's breakfast which I would probably do completely differently nowadays if I had the time, but at least it worked (works)
Rather than directly running shutdown.exe, what you could do is call a vbs script which displays a message box with a timeout in it (I use these kind of scripts for other things - like updating Start Menus), which then calls shutdown.exe.
What difference is there from using normal computer keyboards? None really - same bacteria involved, in keyboard there's more places for them to harbour; so in my mind that would make tablet type devices a little better in that respect. Some of the laptops I've been working on in the last couple of weeks have certainly been home to some interesting life forms
This may sound a little odd but here goes. What are the hygeine issues involved with having a tablet shared amongst so many people? I know someone who works in a well know DIY chain and they have to use an antibacterial wipe on the touch screen tills inbetween users which is just changing from one person to another?
What burgemaster said
Our current scheduled shutdown is a self-written AU3 script so that the users get a countdown to abort.
Unfortunately it doesn't appear to work on Win7 so this might be very useful if you can get a warning/cancel message..
Could an additional task be added previous to the shutdown to display a warning / cancel message?
Yup it is indeed, great weekend last year hope this years is just as good
That's in Blackpool isn't it? Bit far for no time off to go there lol.
Sounds a fun event and a nice day out. I am looking forward to the R3play even in November you should come up to that
[url=http://www.risingjerseys.net/mlb-jerseys/]Wholesale MLB jerseys[/url]
[url=http://www.risingjerseys.net/nhl-jerseys/]Cheap NHL jerseys[/url]
Yes the forum is the best place for questions more people will read it.
I recon the problem is to do with the Raid. If you don't want to use raid at all you need to go into the raid BIOS on boot up (usually CONTRL & M when it boots) and delete the raid array. BE AWARE THAT THIS WILL DELETE ALL DATA ON THE RAID ARRAY SO IF YOU ARE NOT SURE WHAT ON THERE DONT DO IT!!!!!
Then you need to go into the bios and set the Motherboard Raid setup from RAID back to normal. This way you get up to 4 seperate normal hard drives rather than a RAID array. Windows 7 should install on that no problem.
Like you I have nothing but utter contempt for Capita. You were lucky we paid £24,000 for the privilidge. I now spend my days trying to find ways to undermine and destroy Capita ES and all who sail in her. We avoid giving them money at all costs. Am I bitter and twisted? Damn right!
join the Fronter Admin Forum Categories - Fronter Admin Forum
I think the point is that Fronter won't accept support calls from all your users directly; you need to collate and prioritise your users requests and then have a single contact who raises the issues with Fronter.
If you would like to contact me directly we would be happy to put you in touch with Local Authorities who have established their own help desk but also to speak to you about the support for Malta as part of the delivery. I will send you a personal message also.
Upgrade the BIOS and ask questions in the forum next time rather than the blogs area.
Thanks for the info on the fep stuff. That was doing my nut in
Group policy prefs?
There is a shortcuts option which you can manage the start menu quite effectively without having to worry about the redirection
I would suggest posting this as a question in the Windows or Windows Server Forum...
Im not a CC3 user, but as you say that you arent using CC anymore - I would expect that removing any CC related files from you server should have no impact.
Yes I heard bad things about their anti virus being bloated and hard to uninstall/upgrade
But this box is superb, I'm still surprised everyday at how good it is.
Today I setup a ra sites open. It literally took abonew policy for our boarding boys after 4pm with some extut 5 clicks to do. Very impressed.