TMODAlpha

Thanks, that's what I was after

I meant for virtual desktop machines. How do you license them with ms?

Great feedback, thanks.

Which leads me to another question, if I use old equipment as a fat client running thin station, can I use the license that came with the machine, against the EES agreement and then use that to license the VMs?

Looking at VMware for view in the future.

Hello, Planning a VMWare solution and licensing is confusing as hell. Assuming we will have an EES agreement in place, I have to buy a license per each VM I'm running (max of 2 at first). So I would need either an enterprise license, data centre or 2 standards? Does this work out? I this is the case, can I buy 2 standard 2008 r2 OEM and then use my EES key for standard to license the 2 VMs? Also, I'm looking at VMWare vSphere essentials for around £500 per physical CPU. Does this sound about right? I don't need vMotion or anything like that, just want to consolidate future resources, with a view to upgrade later. Thanks

It isn't me that wants to start it right away. My hands are tied on that. Never tried loop back, but it makes sense over WMI. I'm just restricted on time too which means my play and testing time is minimal. Which means things are going to break.

Didn't think there would be, just going over different methods in my head. This was my plan, problem is people want instant results from the word go. So a gradual transition is the best for this I feel. Waiting until summer just isn't an option at this stage unfortunately. I was going to move the home folders, recreate the users on the new domain and take it from there. Don't have to worry about exchange, it's externally hosted. Because I can't create a new domain and I'm going to have to image machines gradually during term time, are the OUs and WMI filters the best way to do it within the same domain? So that they can use both types of workstation from 1 set of credentials? Also, there is a lot of legacy software that some subjects depend on to be able to teach, if I just cut RM out and then dealt with these after, I fear there would be a lot of lost learning time. Which also means that for some time at least, select people are going to need to be able to log on to both. Think the powers that be want a noticeable difference straight away, but I know if they want that it's going to be gradual rather than done all at once over summer.

I can't migrate the users though straight away (assuming moving them would epically break logging on to a CC3 workstation) so I'm guessing a second domain is off the cards? I still need to leave some machines CC3 while we migrate, but if I use WMI filters (all CC3 are XP) then I can assign user and computer GPOs completely using WMI and blocked inherit for the machines OUs? Different desktops and start menus are fine, as are profiles. As long as they can log in with the same credentials and access a file share that's all they will need. My only worry was user GPOs, but I can get around that with WMI filters until all CC3 workstations are gone. Sound about right?

Yes, its one of those threads again. The school I'm at is in the market for some new equipment on a budget. Got everything planned, and know (hopefully) how to go about it all, involving vSphere and ESXi and SANs and iSCSI 2008 R2 VMs and 7 workstations. The problem I'm facing is how to manage profiles between CC3 and Vanilla workstations. All workstations are eventually going to be 7. My question is this, with my new DC's do I add them to the existing CC3 domain and create everything under an OU with GPO inherit disabled, or create a brand new domain. The idea being that they wouldn't need a CC3 set of credentials and then a Vanilla set of credentials as they moved around the school. Is this only possible with 1 domain? Sorry if that is worded really badly, my brain hurts. Thanks