Search the Community

I just had to post a little report of the awesomeness of the diskpart utility in Windows 2003. The scenario was: I had installed two extra drives to a RAID controllers disk set and after the controllers redistribution of data was complete I needed to extend the partition to inclued all of the new free space. The usual corse of action would be to boot the server into gParted and resize the partition from there taking untold eons of time while the server was offline. I thought why not give google a go as 2008 has a nice quick online resize tool surely something simmilar exists for 2003. Answer, yes there is no GUI but the diskpart utility can do an almost instant expantion into the new space even on basic drives. Extend a Windows Server 2003 disk volume Much quicker and cleaner than the gParted solution and now I have an extra 2 hours at least to fight with other anomolies that may show up. diskpart FTW!

I have two Dell R720's acting as hosts for HyperV. I'm starting to begin to run out of space (<25%), ok, so I'm not in any danger at the moment, but I'm looking at options. The drives currently are 10x 300GB 15k SAS in each server, which are still v.expensive. I was thinking of maybe (for roughly the same price per disk) adding a few 900GB 10k SAS drives and creating a separate VD on the controller (Dell's H710mini) and using this purely as a replication store, thus freeing up space on the primary VD. I was wondering if anyone out there who has experience with this server/controller... 1) Is this actually possible? 2) Would is slow down the 15k drives sharing the same controller? Any advise would be welcome...

When not in use for a while there are red crosses over the drives in our environment. The drives become active immediately, but as we are a school the students aged 6-9 become confused and think the wireless connection is lost (sometimes teachers too). Does anyone know a solution to disable this function?

Dear all, I am hoping someone can help. Yesterday I was trying to set a policy to disallow students from browsing the network and typing in a UNC path to the server, ie \\servername. I enabled the policies "Remove Run from Start Menu" and "Remove Network Icon from Start Menu" and initial testers. However when the students logged in they weren't getting ANY mapped drives at all. Not even their home drives. Therefore this morning I have changed those policies back so they are not configured. However the students still cannot access their mapped drives and I am wondering if there is another reason for this or maybe I have changed something without realising it! They basically cannot see any mapped drives but can see the CD drive as normal. (C drive is blocked but it's supposed to be). Is there any other policies that stop users being able to see mapped drives that maybe me or my technician may have accidentally set?

I have .bat files which determine the mapped drives for different groups of users (admin, teaching, care works etc). For each group of users, a policy is in place that will map the drives automatically when the users log in. This has worked fine for so long, but recently the drives don’t seem to be mapping anymore. I have not made any changes that may be causing this, all the policies and files are still in the relevant places. I do, however, have a script for ALL users, which states the drives that everyone should have. These drives are also listed on their own department scripts. Could this be a reason for why it is doing it?