pantscat

Install vmware converter on each individual VM and then convert the local machine.

I'm surprised that causes issues. Do what @fairm010 suggested then - that'd do the job.

Just treat them as physical machines and use VMware converter to convert them to VMs.

I bought my 60D from DigitalRev a couple of years ago - ordered on a Friday afternoon, and it was sitting on my desk on Monday morning coming all the way from Hong Kong. Same deal as Panamoz so you take your chances. If you're after a non grey import then have a look at Wex Photographic.

Another vote for the Lenovo units - we've got around 40 of them and they're great. About to get another 30 this summer.

It's very sad news. Rik was an amazing performer and had superb comic timing. Plus, the fact the he and Ade could recycle the same jokes and still make it funny was brilliant! Listening to Bad News on spotify and it's making me chuckle while I work!

We've got a shared office for the IT Support team, and then I've got a small office that I use when I need some peace and quiet - pretty lucky, I guess! Knock and enter for staff and students - main office is on a magnetic lock...

Totally depends on the workload and intended use of the server. Also depends upon how much storage you need and how many hard disks you're going to have in the server. Generally speaking SAS drives will be faster, more reliable and more expensive.

Yep and QoS...

That's a good point, but it's only really worth having 1GB to the desktop if you've got a multi-gig backbone - e.g. 10GB or multiple 1GB links that are trunked.

I wouldn't necessarily make this assumption! If you've been asked to draw up a plan then dictate what sort of cabling is installed. For example - I have a network cabling standards document that all contractors have to agree to - it dictates what type (and brand!) of cabling is to be used, how things are to be terminated and other such exciting things! In terms of your plan - it's best to start with a functional design explaining what you want the "ICT system" to do and support (it's probably going to be useful to get buy-in and guidance from management on this). Once you've outlined what you want it to be able to do then it's time to drill down and outline technical solutions that fulfil the requirements.

I think @Jinnatonnixx has highlighted the simplest solution so far. I didn't realise exactly how log shipping worked - that's a nice little elegant solution.

Sounds like you want some sort of fault tolerant cluster. Is it a physical server?

Does make you wonder, doesn't it?!

I've been keeping an eye on this issue for a while now as I'm planning on deploying a couple of 2012 R2 file servers in the summer. Seems that the issue is caused by 2012 digitally signing its SMB packets - have a look at this: How To Fix Windows Server Network Performance Problems -- Redmondmag.com

It'll need some other ports open in order to get policies - have a look at Summary of port configurations in Sophos applications

Surely you'd evaluate them all and see which one fitted your requirements best? Sorry, slightly facetious answer there. In all seriousness I'd look at all options - draw up a specification and see what fits best, then look at customer reference sites, talk to them and make sure it does what they claim. Then lastly get them to do a small scale PoC on site to make sure it's going to work. You're likely to be spending a fair few pennies on this so worth their while.

Definitely this. If you're comfy with using vmware and already have that skillset then Essentials Plus will be more than sufficient. Unless you're doing VDI/Citrix type stuff 3 hosts should be absolutely fine.

Have a look at some Shure wireless mics - I'm pretty sure they operate somewhere around 840Mhz. Plus - they're pretty much industry standard... so they'll definitely work.

I got my Ruckus system (54 APs) up and running in a day... this was for 3 of us to run around and wall mount them and configure the system. This included multiple VLANs, guest access and 802.1x.

Ok - As it's a self signed cert the clients will need to know to trust the certificate - otherwise it could be authenticating against anything and how can it know it's safe? So your options are - either use a "proper" certificate, or add the certificate to the clients' certificate store so that it's trusted. Once you've done this you can then use the NAP features to do what you want to do.

I'm sure a mod will be along in a mo to move this to the right forum. But in the meantime - create a new GPO - navigate to User Configuration > Administrative Templates > Windows Components > Internet Explorer > Browser menus - then look for a setting on the right hand side called "Disable Context Menu" and enable that. That should do the trick.

What certificate are you using? If it's self generated have you told the clients to trust it?

I've not used any personally - but there's quite a good list here: Email Signatures :: Software :: MSExchange.org

You've found the issue with it. At present there's no way to make it put the signature in the "correct" place - it'll simply append it to the end of the email. Your options are to either use a 3rd party tool, or add an exception to the transport rule so that it doesn't add a signature if the subject line contains "re:" or "fw:"...