Customer emails through their Exchange event logs, and you need to read through them.
You *could* move them onto your Exchange box and view them there, but what if you couldnt access the box? What if it was a different version? What if you didn’t want to?
You can view other log types by using the /auxsource flag. Handy 🙂
If you read through my blog, you will find I have had great fun creating DDL’s via PowerShell before.
Well, the fun continues.
If you create a DDL via the PowerShell, it automatically sets the RecipientFilter to DOMAIN/USERS. However, when you preview it in EMC it finds all users across your entire domain;
Whether this is a “bug” or Exchange EMC not being “clear” about what its previewing I don’t know.
However, its simple enough to fix.
If you don’t mind doing so, you can re-create the DDL via PS, appending the
to the command. [OU] can be any valid OU (even the full domain).
If you don’t want to recreate, dig out ADSI edit and find the msExchDynamicDLBaseDN string as required.
Refresh your DD’s, and check the “Filter” tab again. It should now display the correct container, and the correct users will get email 🙂
Found an interesting bug regarding XP2 and Group Policies.
When you apply a Internet Explorer policy to a XP SP2 machine, it only works first time. Any subsequent updates to the policy forces it to actually receive “nothing” via GPO.
http://support.microsoft.com/kb/888254 has the fix, but you have to request it.
Also believe that after applying the fix (and the registry fix also) you need to clear out any local profiles stored on the machines.
Fun fun fun 🙂
Come across a semi-interesting “bug” / “feature” this morning in Server 2003 SBS. Old product, I know, but meh who cares.
If you create a new user with the SBS Wizard, whilst you have a Recovery Storage Group configured (even if it is offline), it will default to creating (or attempting to as you will see) the users Exchange box on that SG.
As you try to login as the new user, you will obviously get “unable to access mail folder”, as the SG is (or should) be offline. Viewing the User properties will also show that they are in fact stored in the RSG rather than your First Storage Group.
Fix is easy enough, and comes in two flavours. Hardcore or Wussy.
Remove the user you just created. Remove the RSG. Re-create the user. Check s/he is on the FSG. Voila.
Open up ADSI Edit.
Locate the user object, then locate the homeMDB string. Edit, and replace;
Recovery Storage Group
First Storage Group
Save, exit, and re-login as user. (Then go delete your RSG).
Personally I prefer the latter, as I always like to ADSI M$’s “features”
Well it seems like any OPATH-based filter in Exchange 2007 has the same issues as my previously posted DDL.
Tried creating a new Addresslist policy today using a OPATH filter –> Guess what, it converted it to LDAP format again.
Quick ADSI edit later and I was good to go 🙂
Come on MS!!
Microsoft have “Passed” ESX. Running Server 2008 x86. On Opteron Hardware (with a max memory of 4gb).
Does this mean Intel-based ESX installations are not supported?
And only 2008 x86???
And on another side-note, Exchange 2007 is now supported under “passed” Virtualization Environments.
Microsoft supports Exchange Server 2007 in production on hardware virtualization software only when all the following conditions are true:
* The hardware virtualization software is Windows Server 2008 with Hyper-V technology, Microsoft Hyper-V Server, or any third-party hypervisor that has been validated under the Windows Server Virtualization Validation Program. * The Exchange Server guest virtual machine: o Is running Microsoft Exchange Server 2007 with Service Pack 1 (SP1) or later. o Is deployed on the Windows Server 2008 operating system. o Does not have the Unified Messaging server role installed. All Exchange 2007 server roles, except for the Unified Messaging role, are supported in a virtualization environment. * The storage used by the Exchange Server guest machine can be virtual storage of a fixed size (for example, fixed virtual hard drives (VHDs) in a Hyper-V environment), SCSI pass-through storage, or Internet SCSI (iSCSI) storage. Pass-through storage is storage that is configured at the host level and dedicated to one guest machine. Note: In a Hyper-V environment, each fixed VHD must be less than 2,040 gigabytes (GB). For supported third-party hypervisors, check with the manufacturer to see if any disk size limitations exist. o Virtual disks that dynamically expand are not supported by Exchange. o Virtual disks that use differencing or delta mechanisms (such as Hyper-V's differencing VHDs or snapshots) are not supported. * No other server-based applications, other than management software (for example, antivirus software, backup software, virtual machine management software, etc.) can be deployed on the physical root machine. The root machine should be dedicated to running guest virtual machines. * Microsoft does not support combining Exchange clustering solutions (namely, cluster continuous replication (CCR) and single copy clusters (SCC)) with hypervisor-based availability or migration solutions (for example, Hyper-V's quick migration). Both CCR and SCC are supported in hardware virtualization environments provided that the virtualization environment does not employ clustered virtualization servers. * Some hypervisors include features for taking snapshots of virtual machines. Virtual machine snapshots capture the state of a virtual machine while it is running. This feature enables you to take multiple snapshots of a virtual machine and then revert the virtual machine to any of the previous states by applying a snapshot to the virtual machine. However, virtual machine snapshots are not application-aware, and using them can have unintended and unexpected consequences for a server application that maintains state data, such as Exchange Server. As a result, making virtual machine snapshots of an Exchange guest virtual machine is not supported. * Many hardware virtualization products allow you to specify the number of virtual processors that should be allocated to each guest virtual machine. The virtual processors located in the guest virtual machine share a fixed number of logical processors in the physical system. Exchange supports a virtual processor-to-logical processor ratio no greater than 2:1. For example, a dual processor system using quad core processors contains a total of 8 logical processors in the host system. On a system with this configuration, do not allocate more than a total of 16 virtual processors to all guest virtual machines combined.
Update: I had a think about this. If MS are supporting Exchange 2007 in Server 2008, but will only support Server 2008 x86….. how does that work?
Beremote.exe may take an excessive amount of memory on the Exchange server while running Granular Restore Technology (GRT) enabled backups to tape
Symantec PWN Again.
The Following TiD explains it;
However I have seen this on none-Exchange servers, and on BackupExec 12 servers also.
Basically to check for it, pop into task manager, enable the “Virtual Memory Usage” column, and see how much the beremote.exe is using.
It “should” be 30mb (or there abounts)
Write a batch file to restart the service and schedule it every night.
Good job Symantec!!