chrisbrown

For clarity, as this confused me the first time I read it. If you want to log on as the local administrator, username "Administrator" or ".\Administrator" If you want to log on as the domain administrator, username "Domain\Administrator"

Okay...I said you don't go buy one. Not you don't keep your old one. If your old scripts work fine, use them. It's not my environment, I don't care what you use. However, for a *new* scripter wanting to learn to do things..there is no point recommending he/she use an archaic technology, like there's no point telling him/her that he/she should buy a 1990 automobile. And when you do...I'll be ready. I had to do this very thing on Friday, hence it being fresh in my mind.

I'm a big fan of Q.E.D.. People don't appreciate the sentiment of the phrase.

I'm not debating that, but it's like writing a batch script or VBScript file. You just don't do it these days. Just like you don't go out and buy a 1990 model car because there's "nothing wrong with it". Try using DStools to reset the password of every user whose username ends with "aa" but is not in the "Admin" OU.

Having adminned (to a certain extent) both Postfix and Exchange, I must say Exchange is a much friendlier service, and is much more extensible. I don't know about you, but I don't recall Postfix (or the *n*x world) ever offering a suitable alternative to DAGs and MAPI integration for Outlook...

Scroll up, sunshine. http://www.edugeek.net/forums/windows-server-2008-r2/68488-server-down-notification-2.html#post615584

If "within minutes" is acceptable for you, then by all means, use SpiceWorks. My script notifies me within seconds. I have ~60 hosts in that script and it tells me within usually 5 or 6 seconds when something goes down. I don't know about your requirements...but that's damn quick.

The Scheduler will dump into your event viewer, you can see this on the "History" tab in Task Scheduler. If you're using PowerShell to do this, I'd recommend throwing this command at the start of your script, it will log everything out to file: Start-Transcript C:\mylog.txt

Sure, DSAdd will work, if you don't mind being stuck in the 90s.

Exchange is all it does. 57 is my staging count, it will soon have over 2000 mailboxes on it. My concern is that CAS is going to become a pain, will probably throw a CAS array in our ESX environment down the track. Also: Pagefile = empty. I've never seen this box page anything, it's a dream.

Dear Everyone in this thread. PowerShell. That is all.

Hi Ian, Full backup will mark the file as backed up, and also (if the application's VSS writer supports it..read:exchange) will roll/truncate the log files up into the main file. Do a copy backup if you don't want to impact your data/backup set. Do a full backup if you are doing your scheduled backups.

You need to enable Basic Authentication as well so they get the popup box...

No. Always no.

As you can see...this particular server is using 14GB for the IS, with only 57 mailboxes. We're currently on our annual holiday, so only 4 of these mailboxes are in use at present. Exchange IS will take whatever it can. This box has 24GB of RAM, and is a dual 6-core xeon.

We have 2600 users spread across three SAN attached servers. FSRM is used on Server 2008 R2 for limiting file types and sizes. EDIT: three servers across three campuses.

Do you have folder redirection enabled for the documents library?

I know this has mostly been covered, but let me say that Exchange 2010 is very supported in a VM environment. Microsoft have strayed away from many other software vendors' approaches here. Microsoft support and even provide assistance with getting Exchange up and running in VMs. Because of the dynamic resource allocation and availability advantages of virtualisation, MS would be mad not to support it. There are even several extensive documents detailing the best way to get this up and running. In fact, provided with the opportunity again, I would be running HyperV on my primary Exchange 2010 box and have one or two VMs on there, purely for the ease of backup and availability. Hope this helps, please let me know if you need any more information.

Excuse my ignorance, as I said I'm not in a HyperV environment at the moment, but could you not just use this Action? screenshot_21-01-2011_8-40 AM.png

You are correct in that snap is built in to SQL, Exchange and Server 2008(R2) these days, and that applications simply talk to the VSS Service and VSS reader/writers to do the backup. The difference, however, is how the applications interact with the backups. For example, WSB will simply dump a vhd of the drive at a particular point in time. The difference, however lies in the post-backup usability. Restoring with WSB is a cinch, however, you must restore to a recovery mode database. Anyone who's had to do this before knows while it is doable, it's a right pain and to be avoided. Some alternate solutions (read: paid) that also use VSS include things like (but not at all limited to) granular mailbox recovery, journaling that actually works, and so on and so forth. I've used StorageCraft's ShadowProtect and CommVault Simpana. Both are fantastic products. They do require a bit of an outlay but the benefits far outweigh the costs. You may at first think WSB is cutting the mustard, but I think you'll find in time you need a more comprehensive suite. My 2c.

I agree that it's simple, but I don't think it's effective. What happens when a student removes their proxy configuration? What happens when a student connects a foreign device that doesn't get your GPOs applied? They can then access this website. The only "effective" method is to apply permissions on the site in a deny all, allow few approach.

Hi weeb, There is no (read: not really) any way to do this. You *can* theoretically do it with some pretty intense AD hacks, but it is definitely not encouraged and your network will break in time. Chris

Hi Ian, I don't use HyperV myself so I'm only drawing on my ESX knowledge. Could you perhaps mount the drive using PowerShell once the machine has booted? i.e. PseudoCode (bears no resemblance to real HyperV commands because I don't know them): $vm = Get-VM "Server1" if ($vm.PowerState -eq "Running") { if (Test-Path "F:\DiskToattach.vhd") { $vm.MountDisk("F:\DiskToAttach.vhd") } } Theoretically you'd go: Is the machine on? (Yes). Is the vhd path accessible? (Yes). Mount the VHD. After Google: PowerShell Management Library for Hyper-V After re-reading this it makes little sense, so I'm really just spitballing. Home this helps in some way and doesn't just confuse you like it did me.

I'm using WSB in my quasi-test environment and it seems to work fine. Not that I trust it as far as I could throw it, it's probably the best free option. Without elaborating further, backup should be the last thing you go cheap on.

Why not just mount the vhd as another HDD in HyperV?