MrBeatnik

Hehe... sounds like it could be the issue!! Crazy as it sounds.

Whic profile are the icons inherent in? ".Default" is the profile all users would get if they don't already have one (new user logging in for first time). "All Users" is the profile most applications like to install things to so that all users can use those applications. Check under both those accounts for the desktop directories, and delete the files. Or am I missing the question here completely?

I think I'm a little late for this thread.... Just for anyone checking in the future, you really need to have snap-ins loaded for licenses metering objects, OR just use the old NWAdmin which will allow you to create license objects on the tree. Once you have the ability to create license objects, it's very easy to configure them (amount of licneses etc) - the screens talk for themselves. You can then just link the reagulr app object from Zenworks 7 to that object in the license metering tab. *Edit* - forgot to answer your quesiton. If the WS is not on the network, then it isn't connecting to the zenworks server, so it therefore cannot be metered.

You should be able to set the permissions on the root directory, and tick the option to apply this to all subdirectories. Although it's definitely wise to take a backup, you shouldn't really have to wipe and replace data... Just use the same tab (Security Tab) for each top level directory to set the permissions accordingly. Should be all fine. Heh, I'm on a Mac now, so I can't give specifics on what you should be seeing!! Good luck!

We have one XP image that is (currently) rolled out through ghost and sysprep, but not "just ghost". In fact, I think that if you do it with ghost without sysprepping, it will likely BSOD because of too many hardware changes (depending on what differences you have between hardware setups). With sysprep, we are aware of all the hardware on all devices, and we include the drivers in the driver store (c:\drivers). We have to ensure that all the directory paths are written in the registry (HKLM>Software>MS>Windows>CurVer#DevicePath). The store is about 1GB these days as it includes 8 years of drivers (or thereabouts)!! Mini-setup runs through each directory noted in the registry setting to check the drivers for all hardware. -You could possibly do the same with hardware without sysprep; If the PC does boot and finds all sorts of different hardware, it would still search the driverstore to see if it knows what that hardware is I think. However, you are likely to have some regitsry entries that point to hardware that doesn't exist and could cause issues. Sysprep and mini-setup doesn't take long... I would recommend, PLUS it cuts down on the image size and makes it nice and clean. You can just install XP on a basic machine, install any stuff you want (i.e. flash), clean out the cache/temp/etc and sysprep it. There are a few steps in sysprep to be careful about (mass storage drivers for example), but it's pretty easy overall. Once sysprepped, boot to ghost and upload your image. You can also use PE to open the sysprepped disk to insert new drivers into the driverstore/registry if you find you missed something.

You can select the root directory (the dir that is shared as the network drive). If you select this, there is a check box to take ownership of all subdirectories too. If you don't want to do the root, but select multiple directories, I am unsure if you can do this in bulk - one by one may be required. I don't think it will hurt to try - select all and if option is there to take ownership then it should be ok. See Take ownership of a file or folder: User Rights; Security Policy; Security Services

If you go into recovery console, you should be able to remove the offending file. Or you could "zap.exe" the file, which will kill a file in use and delete it (Comes in a windows tool kit, can't remember which one), but Windows dllcache may come along and replace it within a matter of seconds. You could also try renaming the file, but the cache may step in again. If it's in use though, maybe turn off any services that may be related to WMP... Always tricky these files in use.

Take ownership? Properties > Security Tab > Advanced > Owner Tab > Select owner + tick replace owner on subcontainers. You want to do this on the server itself, logged in as the appropriate administrator...

If it's from a CD, being a CDA format, it's only sybolic links on the disc that you can see, so a direct "file copy" wouldn't work anyway. You probably can't rip to MP3 for placing on a network under most licenses, if I remember correctly. In similar situations, we have created an ISO and used such tools as MagicDisk to mount the ISO. Provided there is a license available to play the disk "in class", this has not been a problem with copyright holders we have checked with (most CD's in this situation are for teaching - ie languages etc). With certain App Management tools, you can point the application to have permissions on the network directory, rather then the user - in effect the user cannot "see" the ISO file, but the program can. Of course, there is a matter of trust in this situation as with giving them the physical disk - once the ISO is mounted or a physical disk is inserted in the drive, they could use another ISO tool to take an ISO copy. Ultimately, as mentioned, PRS would be required (as clubs/restaurants etc need to play music to public), or a special license (ie if the disk is specifically purchased for classroom environment).

Sounds like it's still trying to connect to the old servers first, and getting bumped up the list until it finally reaches a DC -- timeouts on the old servers are increasing your login times as it's searching the for DC?

That's the truth!

No problems here... Although it is slower IMO. I don't tend to use it so much myself...

Not familiar with this app. The only thing I can suggest is to try checking the backgrounds of the app with "process explorer"; this might show what is keeping it open.

Thanks David, I am aware of this utility and it may well be the solution that we need to go with, but I was really curious if there was a way to get windows to set the first drive letter to use when any device is inserted next without having to use a running service or script when device is inserted. >> I suppose another way of looking at it is WHY is drive I: being assigned instead of E:? What is saying "Use drive I:", and how do I change that specific rule? This service basically takes action to re-map to a specific drive when the pen is inserted. That's all fine, but it's another service on the desktop. As usual though, MS probably doesn't have a way to set this and a third party tool (or own script) may be the only way... Thanks for your input though!

If you have software restrictions, then are you going to have trouble running any solution? What software can you run? Any Exe? You could compile a script to run. AutoIT or similar may be quite handy in this situation...