Skip to main content

User Profile Management in VDI deployment

There are millions of ways to management and contain the user profiles, here's one:

Even so, we’ve found that profiles are still accumulating across machines, and occupying more space on the hosted desktops than we’d really prefer. So we had to come up with a way to get rid of these leftover profile remnants. That’s where Delprof.exe came in.

Great utility, yes, but almost useless in the logout script because it won’t delete the current user’s profile (as it’s still loaded at that point). We needed a different way of handling it, so I came up with this little batch file-wannabe that is scheduled to run from the VirtualCenter server on a nightly basis:

dsquery computer “ou=Hosted Desktops,dc=example,dc=com” \
-o rdn > vdi-list.txt
sed -f stripquotes.sed vdi-list.txt > vdi-list2.txt
for /f “tokens=1” %1 in (vdi-list2.txt) do \

delprof.exe /q /i /c:\\%1 /d:1
 
Read the rest.












Labels:






































Comments











Post a Comment






























Popular posts from this blog



















Security: VMware Workstation 6 vulnerability




























vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus




















Post a Comment









Read more






























Splunk that!




























Saw this advert on Slashdot  and went on to look for it and found the tour  pretty neat to look at. Check out the demo  too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE  and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op




















Post a Comment









Read more