scifidale

+1 for opendns, it wont be able to identify the user normally because it works outside of the lan but you would be able to easily see whats being accessed. It can both log and filter.

Ah mondays eh dont you just love em...

When you ran the quick deployment setup (presumably) did you specify an AD group or user (that you are using to test with) for the published desktop?

Firstly, I would check what your oracle DB is as they are a little behind and their licencing for vm's could be a little funky depending on how you provision the vm and what the physical box has. Veam can handle all those requirements and is actually extremely good a replicating and DR restoration (it will allow you to specify a re-ip policy at the dr site if you need it and you can directly powered on a backed up vm and then svmotion it back to the correct lun with veam software). I am assuming that server-b will be a cold standby should server-a go pop, depending on how you configure your replication dont forget that dataloss may occur depending on where in the replication cylce you are when server-a dies. Also with vmware on SD card you have a single point of failure right there, not really too much of a worry but if you are teaming nics and having redundant power supplies etc a single SD card maybe of concern for resiliance. Because you have 64GB in each server you will need to purchase the correct edition which by the sounds of it is essentials (not essentials plus as you wont need vcenter), also if you need to update your esxi software which does happen occasionally then you will need to powerdown all your vm's to reboot the host (possibly not a problem but depends if you pay much attention to your 5 9's metrics). By the same system are you going to buy identical kit for all 6 offices or import their kit onto your new virtual environment. Do not rush this otherwise things could go horribly wrong, what I will say though is actually scale your storage correctly. Have you run iometer or similar to gauge how hard your storage is getting hit on your physicals so you know whether you need 15k drives for some vm's or can manage with 7k drives for the rest. I would without looking into it stick the DC's system drive on 15k and the ts box on 15k and then the file storage on 7k drives. The biggest mistake at the moment people make is judging their storage needs solely on disk space!

Does xenserver support hot adding hardware, I haven't managed to play with that yet, if it does could you remove the vnic and readd another one perhaps!? Or perhaps you could force a shutdown through the host cli XenServer Documentation

+1 for vmware convertor, the current versions will allow you to convert from hyper-v and also 3rd party backup images

I guess you've probably figured this out by now but just in case, you will need to set up a new virtual machine vswitch for the 2nd physical nic. When you are configuring ESXi dont think of physical nics in the traditional sense think of them as Uplinks. For virtual machine traffic you do not set an IP address on the physical nic, just configure the vm's with the correct physical route to the network they need to access i.e. vnic connected to vswitch one for 10.x.x.x traffic and or vswitch two for 192.x.x.x traffic and configure the vm's networking as you would normally within the guest OS (be it a windows vm or a *nix vm).

They've touted the fast boot thing on all of their previous OS's, what they never say is that boot time doubles every time you actually install anything on it!

Terminal services works great for us and I dare say is more cost effective than VDI at the moment as all our user only need standard officey apps, so yes VDI is better for higher end apps, but at the mo we dont need it. My original post was assuming that you would stay at 10 endpoints and not be looking at expanding up to 90, still I think I stand by my original point as we can quite happily manage around 50 RDP connections to modest hardware which saves us a bucket load on licencing.

Why would it have to be powerful, with that budget you could buy a bog standard server, and use terminal services, buy a few wyse s10 thin clients and push settings out with ini file through a ftp site. guess it depends on what the computers will be doing though, but just for standard RDP traffic with officey apps 4-8gb, should be plenty man enough.

Scrap that I've been looking to much for technical reasons why the requests are not being sent, in the end it was down to the user clickity clicking dont send response without reading the pop up box.

We have symantec at our place, (not my choice), its clunky, fails at the slightest thing and the new version needs a reg hack to backup a 300GB data partition onto a storage server. I'm plodding on with it for the time being and am hoping to be able to dump it for vDR when I virtualize our servers in the hopefully not to distant future.

HI all, First post in edugeek (I normally hang out at certforums but this place looks cool too). I've got a rather odd issue for one of our users in that when I or anyone sends a meeting request to this person and they accept the meeting the creator does not get an acceptance receipt. So when you open the meeting whilst all the other attendee's say accepted or declined this users just says none even though they accepted the meeting. I cannot see any options within the users outlook that looks wrong I would be grateful of any pointers as my googling is not really showing up anything helpful. Regards Dale