ChrisMiles

Our setup is almost identical to yours expect that students also have roaming profiles and we don't include the local start menus since even staff are not permitted to install their own software. Students having roaming profiles can be quite a pain because they are easily corrupted when they irritatingly force off laptops when they're in the middle of syncing. But I think it creates a sense of continuity for the students which makes it easier for them to get used to the software. On the whole, folder redirection policies can be a right pain in the posterior to set up but once they work its fine.

First you need to solve this networking issue with the second physical server. Have you configured your test DC with dhcp, or does your second server have a static IP on the same subnet as the DC? Have you added the second server to the new test domain as a member server? Check all these things and make sure that it's fixed before starting with virtual networks. If you want a quick rundown on the different types of virtual networks: External virtual networks share the physical network adaptors in your host and connect your VMs directly to your physical lan as separate devices with their own IP address etc. Internal virtual networks allow the VMs to communicate with the host server on a seperate subnet from your physical lan. The VMs cannot communicate with your physical lan. Private virtual networks allow multiple VMs to communicate with each other on a seperate subnet from your physical land. The VMs cannot communicate with your physical lan. In this case it sounds like you want to add an external network using the Virtual Network Manager in Hyper-V Manager. Select the physical network adaptor on the host. Then make sure your VMs have a virtual network adaptor installed and that it is configured to use the new external network. Once you have done that the virtual machines will appear as if they were physical servers on your network and will use DHCP or require a seperate IP address within that subnet.

Can you be more specific as to what you are trying to achieve? Do you want an entirely virtual network for VMs separate from your physical lan? Do you want to connect your VMs to your physical lan? Are you using any VLANS?

All users have permissions to update this information for their own user account in AD, it is by design. It includes most of what is on the front page of the user properties screen as well as addresses and such. There is no way to prevent this without using ADSI edit to remove permissions and modifying the schema.

You'd be supprised what you can do with just domain user permissions. Users can, for example, edit certain fields on their own AD user, which is pretty annoying. However, when it comes to MMC stuff, they obviously don't have permissions to modify anything, they can, however, view almost anything, however, one question does present itself: Why do you have the AD management tools installed on the student computers in the first place? Anyway, regardless of what MMC snapins you deny, they can still use VBScripts or powershell to access data on pretty much anything if they really wanted to.

Just thought I'd point out that you don't have to run 2008 r2 core to run hyper-v, it works perfectly fine on the full install. Also as has been said, hyper-v can control what happens to the virtual servers when it attempts to shut down. Also, using hyper-v, I'd strongly recommend having at least one physical DC.

That's how I would do it at any rate, it worth a try. As for where to apply it, it doesn't really matter I guess, apply it at the highest level to encompass all the computers you want affected, I guess in this case, the OU which contains all of your "sites". Don't link it in each site, there's no need.

This may help you: How to set default printer permissions on all AD printers Have you considered controlling things like this in software using something like Papercut? This is what we use, in the extremely unlikely event that a student managed to connect to a printer they shouldn't, any print outs they do are logged. Not that any of them ever have.

This is the cheapest dual dvi card I could find: Zotac GeForce GTS 450 810Mhz 1GB PCI-Express HDMI OC (ZT-40503-10L) - dabs.com Not an 8000 series card, seems like the only 8000s you can get now are dvi/hdmi/vga.

We used GPP. Some of the drives have item level targeting for different OUs but the policies don't have a delete set up to remove the drives since the drives don't change like yours do, however, the laptop users who work from home have never reported any issues with mapped drives or slow logins. We used to use scripts, which works just as well and are easier to customise if you're familiar with vbscript, we just moved it to GPP just to keep everything together.

In my experience, mapped drives to servers which don't exist haven't caused problems like this, even with Reconnect enabled. However, I would combine the policies into one, changed the "Delete All" one to have no Item level targeting and then the individual drives with the appropriate settings and item level targeting on the off chance that the Delete All is getting confused about whether it should apply or not. Other than that, if you want a work-around, make a log off script which removes all mapped drives.

You do not need the Delete map drive as has been pointed out, the policy is not applied on a different site. In my experience, making sure the Reconnect option is not checked should be enough to ensure that the drive is not carried over into another logon session, however, also selecting the 'Remove this item when it is no longer applied' option on the Common tab should also ensure that it is removed.

Long shot but are you using 64-bit because I see reports of having to also set the same value in: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{323CA680-C24D-4099-B94D-446DD2D7249E}\ShellFolder for it to work on 64-bit.

Try this: Bibliotheken, Favoriten & Co. im Navigationsbereich des Windows Explorer entfernen

If you have to go with a different reader, I'd recommend foxit reader, however, we use Acrobat Reader 10 on our windows 7 machines without issue. Try adding a student to local admin group and see if it works to rule out any profile/group policy issue.

Sysprep can fail to re-run if windows is not correctly activated each time before it is run. This is because windows only allows a maximum of 3 syspreps on an un activated copy of windows to prevent you using sysprep to bypass the grace period. Make sure your image is activating against KMS before attempting to re-sysprep.

You won't need to reinstall SQL to move it at all. All you need to do is execute the following statement: USE Master ALTER DATABASE sims MODIFY FILE ( NAME = sims_log, FILENAME = 'E:\SQL Logs\sims\sims_log.ldf' ) GO Where 'sims' is the name of the database, 'sims_log' is the logical name of the database file, and the path is obviously the full path to the log file. Make sure you check these values are correct for your install. After that shutdown the SQL services, move the log file to the new location (and ensure the file name is correct) and the start the SQL services again. For more information see: Moving User Databases

You are syspreping every time arn't you? It needs to be done on each machine, not just at the end. If so, does windows 7 install manually ok on the target machine? The only problem with this way of making images is that there is no opportunity to add disk controller drivers (ie F6 during install), and instead relies on windows having drivers available.

It definitely works as long as the host configuration is set to Windows 7, however, I have only used this on 0.29 and 0.30. I'd recommend upgrading to 0.29.

Don't panic, this is by design. Fog uses a special kind of Disk image when you select partition image with a windows 7 machine to allow it to handle the extra 100mb system partition which comes with windows 7. The 000 files should still be compressed, but as with the disk images, a folder containing multiple files is used instead of one gzip file.

Cant really advice much except to say that I have fog 0.30 and 0.29 working fine in Hyper-V on Ubuntu 10.10 Server (the desktop version doesn't seem to work properly with hyper-v still) so I doubt its that unless there's something with Centos which is causing the problem. I will say though that the performance of fog on a hyper-v server is acceptable but poor compared to running it off even a decent desktop especially 0.30, but that's just my experience. Might be worth doing a physical install as a test to make sure its not an OS config issue.

It means either you don't have permission or there are locked files in the profile folder which are preventing the folder from being deleted. This should not normally happen. There might be some issue here you need to investigate (ie why is there locked files in a profile which is not loaded). To disable this message comment out the line: MsgBox "Error"

Are you sure you didn't just forget the default password? We've over 60 Samsung printers and they all came with a stupid default login of u:admin p:sce00000 or was it sec00000, one of those anyway

I don't know how feasible it is but if it's not too much of a pain I'd suggest rebuilding your image on the machine with the smallest hard disk you have, should fix this issue. Otherwise you could try and use something like ghost to move the image to the smaller disk after you've syspreped it of course, and then upload another image from that machine.

########################## # An error has been detected! # ########################## Resize test failed! ntfsresize v2.0.0 (libntfs 10:0:0) Device name :/dev/sbd2 NTFS volume version 3.1 Cluster size 4096 bytes Current volume size: 314569216 bytes (315MB) <--- Current size of partition on disk? Current device size: 314572000 bytes (315MB) <--- Current size of disk? Volume size: 465883648 bytes (466MB) <--- Size of image partition to write? ERROR: New size can't be bigger than the device size. If you want to enlarge NTFS then first enlarge the devicesize by e.g fdisk. ############################ # Computer will reboot in 1 minute # ############################ It looks like you are trying to write a 466MB partion image to a 315MB disk to me. FOG can expand partitions to fill a disk but it cannot shrink them to fit. When you upload a single partition image to fog it first resizes the partition to the smallest size it can to help accommodate smaller disks, however, because of things like MFT data and file fragmentation it will never be able to reduce the partition to a number very close to the amount of actual data on the disk. You can try aggressively defragmenting the disk (get all the data moved to contiguous blocks at the start of the disk, you'll need something other than windows defrag for this) on the original machine but NTFS usually allocates MFT data around the middle of the disk and this can't be moved when windows is running. Are we still talking windows 7 here because 466mb seems way too small for even a blank windows 7 install anyway?