When one of our users is on holiday they will set their Out of office message and change the Out of office rule to forward all emails received to a colleague. This has always worked very well for us while we were using Exchange 2003, but now we have some of our Mailboxes on Exchange 2010 the behaviour seems to have changed (for the worse).

Exchange 2003

Mailboxes located on Exchange 2003 will send the following message to the person defined in the Out of office forwarding rule. Notice that the original senders email address (in this case my personal email address) is shown.

Exchange 2010

When the Out of office forwarding rule kicks in for Mailboxes on Exchange 2010 the email is forwarded on as normal, but notice that the original senders email address is not shown on the forwarded message.

This causes us a problem, because the whole idea of having emails forwarded on to somebody else is so they can deal with the enquiries and orders that come in while the other person is on holiday. If the person dealing with the forwarded emails needs to contact the customer, Exchange 2003 made this easy by showing their email address - Exchange 2010 seems to make this impossible.

Is there an option we can change to make the original senders email address show, have Microsoft removed this feature or is there at least some workaround we can implement that will allow us to have what we need?

Update 1

I have tested this with various combinations of Outlook and Exchange and here are the results of the test. As you can see, something has definitely changed in the way Exchange 2010 behaves with forwarded Out of office messages. Does show/Does not show is relating to the original senders email address.

+--------------+---------------+---------------+ 
|              | Exchange 2003 | Exchange 2010 |
+--------------+---------------+---------------+
| Outlook 2003 |   Does Show   | Does not show |
| Outlook 2007 |   Does Show   | Does not show |
| Outlook 2010 |   Does Show   | Does not show |
+--------------+---------------+---------------+

Here is the (mildly sanitised) output of Get-RemoteDomain | fl. I'm not entirely convinced this has anything to do with it though, as these settings are all for outgoing mail to domains other than our own.

RunspaceId                        : 1002c62b-9f50-47a0-8862-1d635c4dbdba
DomainName                        : *
IsInternal                        : False
TargetDeliveryDomain              : False
CharacterSet                      : iso-8859-1
NonMimeCharacterSet               : iso-8859-1
AllowedOOFType                    : ExternalLegacy
AutoReplyEnabled                  : True
AutoForwardEnabled                : True
DeliveryReportEnabled             : True
NDREnabled                        : True
MeetingForwardNotificationEnabled : False
ContentType                       : MimeHtmlText
DisplaySenderName                 : True
TNEFEnabled                       :
LineWrapSize                      : unlimited
TrustedMailOutboundEnabled        : False
TrustedMailInboundEnabled         : False
UseSimpleDisplayName              : False
NDRDiagnosticInfoEnabled          : True
AdminDisplayName                  :
ExchangeVersion                   : 0.0 (6.5.6500.0)
Name                              : Default
DistinguishedName                 : CN=Default,CN=Internet Message Formats,CN=Global Settings,CN=WIDGETS,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=corp,DC=acme-widgets,DC=com
Identity                          : Default
Guid                              : 0f601b72-7249-47cb-8f51-321c5d070d7f
ObjectCategory                    : corp.acme-widgets.com/Configuration/Schema/ms-Exch-Domain-Content-Config
ObjectClass                       : {top, msExchDomainContentConfig}
WhenChanged                       : 25/01/2011 17:20:34
WhenCreated                       : 10/10/2007 12:17:57
WhenChangedUTC                    : 25/01/2011 17:20:34
WhenCreatedUTC                    : 10/10/2007 11:17:57
OrganizationId                    :
OriginatingServer                 : dc2.corp.acme-widgets.com
IsValid                           : True

Update 2

The suggestion by Holocryptic to use the option Keep message intact seems to have done the trick. It's a pain to have to do this to each computer, but so far the best "solution" I've had. Ideally I'm still looking for something server side like Exchange 2003 was, but Holocryptic is most likely to end up with this bounty.

We have 2 Exchange servers, one Exchange 2003 and one 2010. We are migrating from 2003 to 2010 and this has been largely painless, but we have a niggly problem I can't figure out and the documentation isn't the clearest thing in the world.

When a mailbox moves from Exchange 2003 to Exchange 2010, and the client is Outlook 2007 or greater, the Out of Office dialog changes to include internal and external OOF message options. I understand the reasons behind two separate messages, but it does not work well for us (people forget to change both messages, complain about having to set the same message twice etc.) and I want it back to how it functioned in Exchange 2003 - a single OOF message which is sent to both internal and external senders.

I cannot for the life of me find any options in the Exchange Management Console, and I can't see any PowerShell-only options to make it go back to Exchange 2003 style functionality. Does such an option exist, and if so where on earth is it?

This is a Canonical Question about Licensing.

Questions on licensing are off-topic on Server Fault. If your question has been closed as a duplicate of this question, then this is because we want to help you understand why licence questions are off topic rather than just telling you "it just is". In all likelihood, this question will not address your question directly, it was not meant to.

I have a question regarding software licensing. Can the Server Fault community please help with the following:

• How many licenses do I need?
• Is this licensing configuration valid?
• What CALs do I need to be properly licensed?
• Can I run this product in a virtual environment?
• Can I downgrade this product to an earlier version?
• Am I entitled to feature X with license Y?

This may be borderline Server Fault, so I'm cool if it's decided this question is migrated elsewhere.

As a sysadmin, I am responsible for responding to any monitoring alerts which occur out of hours. I have a company issue BlackBerry, so if a monitoring alert is sent, I can be notified. This is great .. provided I'm not in another room or asleep. Yes, it makes a noise when an email is received, but if I miss that little noise that lasts about 2 seconds, I've missed the alert.

What I'm looking for is an app (paid for isn't a problem) which can sound an alarm when an email is received that matches certain criteria that does not stop until I dismiss it.

Criteria would be any of the following (bonus points if I can mix and match criteria)

• Sender address
• Message subject
• Recipients

This is primarily for a BlackBerry, but apps for other smartphones might be beneficial to the greater community.

I've spent the better part of this morning wrestling with this one, so I'm sharing it in case others in my situation experience the same problem.

We are currently in an Exchange 2003/Exchange 2010 co-existence period. There are a handful of test mailboxes on our Exchange 2010 server, the rest are on Exchange 2003 and our Offline Address Book generation server is currently the Exchange 2003 server.

Yesterday somebody left the company, so we followed our normal procedure and hid them from all Exchange address lists and waited overnight for the Offline Address Book to be rebuilt. When I got in today, the offending user was still listed in our Offline Address Book. For reference, this users mailbox is on the Exchange 2003 server.

I checked the event logs on the Exchange 2003 server and no warnings or errors were logged in the early hours by the Microsoft Exchange System Attendant service during the OAB Generation process. Thinking this was just a fluke, I manually rebuilt the Offline Address Book with the same results (no warnings/errors and the user still in the Offline Address Book).

There are no synchronisation errors in Outlook and I have verified (using Exchange System Manager on the Exchange 2003 server) that the Offline Address Book does exist and is still being created in the early hours of each morning, as well as when I manually rebuilt it this morning.

We're a little behind in the virtualization game, I'll have to admit. We currently have nothing virtualized, but I'm trying to change that.

We want to get our feet wet with virtualization and get a feel for it, so I am going to propose for next year we get a server and virtualize 3 rather under-utilised (and incredibly old) non-critical servers.

I know virtualization is all about SANs, but unfortunately we don't have one (all our servers are DAS). The question I have is if I get a server (probably a HP DL380 of some description) with DAS, are the guest VMs (under-utilised don't forget) going to suffer badly as a result? My current thinking is to put Hyper-V Server 2008 R2 as the host, if it makes any difference.

I'll give a quick run down of what the 3 servers do below. I know this isn't an exact science, but roughly speaking - do you think DAS will be OK?

Server 1
Runs a legacy HR system which is accessed maybe once or twice a week. This has a SQL Server 2000 backend which also runs on this server. This thing is archaic (I don't know when HP stopped branding ProLiants Compaq, but this proudly displays the Compaq logo on the front).

Server 2
Runs some emulated printers for our AS/400 and prints the output to some real printers. This runs happily on an oldish PC with W2K3 and 2GB RAM.

Server 3
Runs a server for a BI product, however all it actually does is at 4:00AM imports a ton of data from our AS/400 and compiles it into a file (this takes about half an hour). About 15 users then periodically (maybe once every few days) download this compiled file (~100MB) to their local computer. The download is user initiated, so there's no real defined access pattern.
This is also on a PC running 2K3 but with 3GB RAM.

Update
We've looked at virtualization several times now, but because of our lack of SAN and the many advantages it brings, we have dismissed virtualization as an option each time.

I know some of the pitfalls of putting these VMs on DAS (lack of HA etc) - and that is OK for these machines. If the host were to fail, it would be an inconvenience rather than a full blown disaster.

I'm looking at this more of a consolidation project rather than anything else. The 3 servers are slated for replacement next year anyway, and like I said they are getting rather old, sit mostly idle and are big tower machines using a lot of space and electricity. In my opinion, 3 new servers (however basic) is still overkill for machines that sit doing very little all day.

I have a need to use Windows XP Mode in Windows 7 to run a legacy application, so I downloaded, installed and configured it on my machine as a test without any issues. The problem I am now having is I have done the same setup on the machine which needs to run the legacy software and WSUS seems to be getting confused as to which VM is which.

Here's what I have done so far on both machines (which seems pretty reasonable to me), can anybody see any flaws in my process?

• Download and install the .msu file to enable Windows XP Mode
• Download and install Windows XP Mode
• Download and install the .msu file to enable Windows XP Mode without hardware assisted virtualization
• Set the network mode to use the physical NIC (instead of the default NAT)
• Renamed the VM to HOSTPC-XPMODE
• Joined the VM to the domain and moved it in Active Directory to the appropriate OU

For the sake of argument, we'll call the 2 Windows 7 machines PC001 and PC002 (with PC001-XPMODE and PC002-XPMODE as the names of the VMs).

When I go into WSUS, it will show me status information for either PC001-XPMODE or PC002-XPMODE, but only one or the other - never both at the same time. It's almost as if WSUS is getting confused because it is an identical machine.

Am I missing something fundamental, or am I using it not actually as intended? This blog entry from the Virtual PC team talks about joining the VM to the domain, so I don't think I'm using Windows XP Mode incorrectly (but feel free to correct me if necessary).

I am having a really hard time getting an iSeries (AS/400) machine talking to my new Windows Server 2008 R2 box using the QNTC file system on the iSeries.

I had similar problems getting it to initially talk to a Windows Server 2003 machine, but enabling the local Guest account on the 2003 box solved that one. No such luck with the new 2008 box.

When I do a WRKLNK /QNTC/SVR01 on the iSeries (which should show share listings, and does on any 2003 boxes) all I get is (Cannot find object to match specified name.).

I know the iSeries likes the same username and password on the remote server, but unfortunately for us this is not the case. Anyhow, it does currently work with different username/password combinations on a 2003 box.

To try and get the wretched things talking, I have made the 2008 server pretty open but the iSeries will not see shares on it. I have enabled the local Guest account, turned Windows firewall off, set the share permissions so Everyone has full control but to no avail.

I read something on the internet about the iSeries only being able to handle NTLM authentication (and I understand by default that Server 2008 R2 only uses NTLMv2 and has NTLM disabled), so I made a special group policy for the server and tweaked all Group Policy settings under Computer Configuration\Policies\Windows Settings\Security Settings\Local Policies\Security Options but the iSeries STILL won't see it.

Looking in my iSeries job log, I don't appear to be getting any error messages either.

We have a team of programmers who do all the system administration of the iSeries, but they are stumped for ideas on their side, and I'm stumped for ideas on my side.

This is driving me crazy now, and if anybody has managed to get an iSeries to talk to Windows Server 2008 R2 using QNTC I would be very appreciative of any suggestions, be it on the Windows side, iSeries settings or even IBM PTF's that might patch anything. The iSeries is running V5R4 and I have *SECOFR privileges on it, if it helps.

One final (most important!) note - The programmers think it's my system being tricky, and I think it's theirs - please prove me right :)

Rationale this belongs on ServerFault rather than StackOverflow - I already have my program which gets the value, I am querying the value returned and what it means.

I have an in-house program which audits our company PCs, and one of the things it checks is the speed of the processor. To do this, it queries the Win32_Processor WMI class and gets the value of CurrentClockSpeed.

We were playing with the data today and found an anomaly with some of the speeds being reported incorrectly (for example, CurrentClockSpeed said 1.0GHz, whereas the CPU name said Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz [Confirmed it is in fact 1.83GHz]). I did a bit of digging on the internet and found this blog post which might explain what is going on.

My initial thought was that I could change the program to instead get the value for MaxClockSpeed instead of CurrentClockSpeed, but Microsoft's documentation doesn't clearly define what this will return. What I mean by that is will this return a value which is its actual maximum speed (say if it were overclocked) but which it would not normally be running at, or would it return what I expect, which is its maximum speed under normal (not overclocked) conditions?

My question is simple, and I think I know my answer - I'm really after a confirmation from others.

Obviously, if my WSUS server dies I will have some hefty downloads to do once it is back up, and that's not a problem. I was thinking more of the database behind WSUS - should that be backed up?

What I think would happen is that it would be just like setting WSUS up again for the first time - change the group policy and the WSUS server will then build its database of computers and their installed updates from scratch.

Am I right in my assumptions, or will it do something unexpected?
Is it better in the long run to just back the database up, say once a month and be done with it?