Group Policy computer settings not applied to Windows 7 Computers

We started moving a few people to Windows 7 this week and I discovered that none of the computers were getting the computer GPO settings applied. My company tends to keep domain computers in the default AD “Computers” container.

It appears that Windows 7 computers left in the default “Computers” container will not recieve the computer settings from any GPO’s that would otherwise be applied.

I haven’t been able to confirm this as a “by design” feature of the new OS but it is definitely the case for me.

Once I moved the Windows 7 computers into an appropriate OU and rebooted them computer settings were applied with no issue.

I guess Microsoft finally got around to actually enforcing one of their best practices.

Interesting.

Adding aliases to Distribution Groups using Powershell

On several occasions at work I have been asked to add email aliases to distribution groups for testing purposes. Depending on how many you have to add, in my case 30 or more, doing this through the exchange systems manager just won’t do. I mean, what self respecting systems engineer is going to copy and paste all these addresses one by one? Not me…did that the first time in a crunch and not doing it again.

Anyway, since there is a need for multiple email addresses we usually identify each by using a basic format followed by a number increment (user1, user2, user3 and so on and so forth). Since the aliases all have the same email address prefix I figured this was ripe for some powershell scripting so without further ado here is what I came up with.

#gets the distribution group name and puts it in a variable
$group = get-distributiongroup “example_group

#enter starting number here
$i = 1

#enter email prefix
$user = “user

#email domain address
$addr = “@yourdomain.com

#This is the loop. It will continue adding addresses until the ending number is reached.

do {
$newaddr = $user+$i+$addr
$group.emailaddresses += $newaddr
set-distributiongroup -Identity $group -EmailAddresses $group.emailaddresses
$i +=1
}

#enter ending number in place of “40″
while ($i -le 40)

The above example will create email aliases for the distribution group called “example_group” starting with “user1@yourdomain.com” and ending with “user40@yourdomain.com”.  If you wanted to increment another number just change the starting and ending numbers in the script.

Control Panel Mail Icon missing from Vista x64

To access the Mail Icon in Control Panl on Vista x64, go to Control panel home, choose additional options and then “View 32-Bit Control Panel Items”. You will then see Mail as an available option.

Mailbox size GUI script for Exchange 2007

This is an amazingly good script that I found while searching google looking for a way to get mailbox details in a readable format using the powershell. Click on the link below to get the details.

Many thanks to the poster, Glen Scales, for sharing his extensive knowledge on the subject of Exchange development and scripting with the rest of us.

Good stuff indeed.

http://gsexdev.blogspot.com/2008/05/version-5-of-mailbox-size-gui-script.html

Auto-response to external (Internet) addresses with Exchange 2007 and Outlook 2007

Recently I was asked to setup an email address that would be used for resume subittals for a position my company is hiring for.  I was informed that when emails were recieved by this account an auto-response would need to be generated that attached a questionnaire (part of the weeding out process) as part of the automatically generated reply.  After thinking about the best way to accomplish this here is what I came up with.

I set up a mail enabled public folder called “IT Jobs” giving the folder the appropriate email address.  Next, using the public folder “Folder Assistant” I created a rule to be applied to all messages that were received or posted to this folder.  The “Folder Assistant” can be found by right-clicking the public folder you just created > going to “Properties” > then clicking on the “Administration” tab.

Once you are there , just click the “Folder Assistant” button to get started creating your rule. I created my rule by checking the “Reply with” box under the “perform these actions” section of the folder assistant.  Next, in order to create my auto-response template I chose the “Template” button next to the “Reply with” checkbox to bring up a blank email message.  You do not need to put anything in the TO:, BCC:, or other fields unless you want to.  After you are done typing out the email and attaching any documents you can save the message template and click OK to close the windows.  You are now ready to test your auto-response.

One important thing that I discovered while doing this is that none of the auto-responses were working to external addresses.  In order to fix this you must go into the Exchange Management Console > Organization Configuration > Hub Transport > Remote Domains > open Default and go to “Format of original message sent as attachment to journal report:” and make sure the “Allow Automatic Replies” is enabled.  This will allow the auto-response messages to reach the external senders.

Method ‘post’ of object ‘IOWSPOSTDATA’ failed

I found the fix to this error on the following website: http://www.tek-tips.com/viewthread.cfm?qid=1330234&page=1

Below is the excerpt with directions for the fix.

Importing lists from Excel 2007
returns a Method ‘Post’ of object ‘IOWSPostData’ failed dialog. Again,
not really a problem with WSS 3.0 but rather the result of a failed
Application.SharePointVersion() call in the Excel Add-In which results
in Excel attempting to use the IOWSPostData.Post() method to publish
the Excel range which is used with SharePoint Team Services 1.0. By
forcing the version lookup result variable to 2 or greater, Excel will
use SOAP to communicate with WSS 3.0 and the publish request will be
successful. To make this change, open the Excel Add-In EXPTOOWS.XLA
locate in C:\Program Files\Microsoft Office\Office12\1033 by default.
Press Alt+F11 to display the Visual Basic code
editor and search (Ctrl+F) for the line lVer =
Application.SharePointVersion(URL). Comment out that line with a single
quote and add the line lVer=2 so your Intialize() method should now
look like this:

Sub Initialize(List, Title, URL, QuickLaunch)

strQuickLaunch = QuickLaunch

aTarget(iPublishURL) = URL

aTarget(iPublishListName) = List

aTarget(iPublishListDesc) = Title

‘lVer = Application.SharePointVersion(URL)

lVer = 2

End Sub

Sharepoint links don’t open in a new window

This is so frustrating….I’m not sure how Microsoft missed such a simple but important property
in the links webpart. There are always workarounds but seriously…..It doesn’t change the fact that we shouldn’t have to struggle
so hard to make things work the way they should.

Anyway, I found this simple fix on another blog and it worked flawlessly.

Much thanks to the author!