Tricky_Dicky

Ok, that's a new one on me. Do you have a folder at the route of your home share called photos?

You don't need a separate home directory for the iLife software though. As long as the students can write in to their own home directories it will work fine. The only thing to watch out for is sometimes when the students login for the first time it doesn't create the appropriate directories, normally misses Movies. But if you just get each child to manually create them the first time it will work fine. Are you getting a specific error message in a specific program?

Hi, What you normally do with Macs and AD is link them together in what Apple call the Magic Triangle. This is when the Macs OD authentics with the Windows AD. What this allows you to do is use the students normal home directories as they would on a Windows machine on the macs. What sort of setup have you got at the moment? Rich

Bit long winded but: I think you need to enable, via powershell, the ability to change the sharing permissions on calenders through OWA. If you go to This Site it shows you most of the commands available. I've always done the sharing through either Outlook or Mail for Mac and it works well so there is no reason why it can't be done. Rich

What for iOS5 which is due out imminently and then get an AppleTV and attach it to the projector.

I've got one, the TS-639 which is a 6 bay 6TB version. Very nice piece of kit with a lovely front end. PM me if you want to come and have a look but I am in Birmingham.

That is so cool! Tell him to look at an Arduino chip and get some 2 way comms going so you know when it's boiled.

Bit lost as to what you are trying to achieve here. The idea of MDT (or at least the way we are doing it) Is to push out a clean image, normally straight from the disc, then get MDT to install any Drivers, Applications, packages and then capture that image back all syspreped up and ready to be deployed. What folders are they?

Just wondering, does anyone have an idea as to why when the client starts to PXEboot it gets to TFTP Download: boot\x64\pxeboot.n12 and just keeps repeating that message over and over until it eventually times out and fails?

Seems strange though that mine is showing up at 800+Mb where as BoosMan is at 168. Also doesn't help that mine will now not boot! Not sure what I've changed but I'm pulling my hair out.

That's irritating... When you created the boot image, did you do the following: Setup MDT; import an OS, import Drivers, create a task sequence, update deployment share Setup WDS; import a boot image and point it at the deploymentshare one create above? Thanks for the help Rich

Is that the size it says within WDS boot images?

Ok this is weird. When I create the boot file from within MDT is outputs it to C:\DeploymentShare\Boot and in there the wim file is 168Mb, however when I import it into WDS it grows to 1024Mb. Any ideas what's going on?

That's more like what I was expecting. Have you compressed that? Any ideas what I've done wrong to make it so big?

Is that your install image or the boot image though?

I'm just working through MDT and WDS to deploy Windows 7 and noticed that the boot image is 854Mb for the x86 and 1042Mb for x64. Is this correct as it seems massive to me? Thanks Rich

Downloading the desktop version now. Will do a backup of the server and then do that as well.

I would put it before first login, after the machine has joined the domain. I presume you are only installing this on the image deployment, not capture? Rich

Just a couple of questions then 1) I heard some where on here that having an EES licence gives you access to MSDN is that true? 2)How does the licensing work for teachers home computers? Can they buy a licence and we just burn the media to disc? Thanks Rich

That's fantastic. Most staff would have just blamed me for having the wrong toner in stock.

Fair enough. We setup Live@edu for our staff here a few months ago and they have taken to it really well which always make a nice change.

That makes more sense, I was wondering why you had a whole Zimbra setup just sat around sending out notifications. Just wondering though, why do you use Google Apps for Students and Live@Edu for staff? Why not have them on the same system?

I personally wouldn't bother with an in house email system anymore, have a look at either Microsoft's Live@Edu or Google's Education Apps.

Personally I would try and remove those smaller switches by either running new cable runs back to your central switches or if that's not practical due to distance then some smaller network cabinets with a 24 port switch in closer to where you need them.

Hi, I think this is possible network related but... I've two identical servers, both setup with Hyper-V using a shared iSCSI SAN and I've installed the failover clustering feature on both. Both machines are joined to the domain and can happily see each other via shares and ping. However I've started to try and test setting up the failover clustering and when I start the validation, I select both machines by browsing to them in the AD but they both come up with the error of "Failed to connect to the service Manager on *othermachine name*". Am I missing something pretty basic here or do I need to configure something specific in regards to the network so they can see each other? Thanks Rich