I have really been trying hard to use a MacBook Pro (Intel) as my primary laptop at work. Being a network engineer in an all Windows environment has made this transition a very frustrating one to say the least. My main source of frustration has been performance, or lack thereof, of the Windows virtual machines running in Fusion. The MacBook Pro I have been using only has 2 GB of RAM and supposedly only goes up to 3 GB (I am still researching this). Needless to say, this was a huge part of the problem in successfully running the Windows VM’s in the background.
On Monday of this week I bought a 2 GB stick of RAM on sale from Microcenter for $30 to bump the memory on the Mac up to its proverbial ceiling of 3 GB. This has made all the difference so far. I am now able to run Windows Vista with a full 1GB of memory and OSX still has 2 GB all to its self. In addition, I found this post http://blogs.vmware.com/teamfusion/2008/09/optimizing-vist.html which gave me some nice tweaks to the Vista VM and now the whole system is running even better than with just the memory upgrade. It still isn’t as fast as I would like it to be or as fast as my Thinkpad T60p running Vista but I am definitely not giving up the ghost just yet.
If I can just disparage the rumors that my MacBook Pro doesn’t go past the 3 GB of memory claimed I might just be a convert after all.
Last week our exchange mailboxes were migrated to servers in a data center half way accross the United States. We needed to leave the existing (old) Exchange 2007 cluster up in order for the mailboxes to be migrated and also to verify distribution list creation and members on the new system. The total migration was to take approximately 48 hours and all existing Outlook clients would need to be re-configured to connect profiles to the new email system.
The morning after the migration is when the issues began. Users opened Outlook as they normally did but with the old exchange cluster still being available and the Outlook client not yet being configured….Outlook connected to the old mail servers. Needless to say everything looked normal to the user and they could even send and recieve mail internally but this added to the confusion.
So…to keep users (Outlook MAPI clients) from connected to the old Exchange 2007 cluster I ran accross this article on Microsoft’s tech net that allowed me to resolve my issue.
http://support.microsoft.com/?id=288894
Adding the correct registry value for the client version was bit confusing to me but I made it work with the below values which should block everything from build 5.2653.11 up to the lastest build of Outlook 2007 with SP1 and the latest hot fixes.
Here is a synopsis of the steps I took from the above technet article along with the values I used for my registry entry.
- Start Registry Editor.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
- On the Edit menu, click Add Value, and then add the following registry value:
Value name: Disable MAPI Clients
Value type: REG_SZ
Value data: 5.2653.11-12.6320.5000 - Exit Registry Editor.
- Restart the Microsoft Exchange Information Store service in the Services snap-in. Restart the Microsoft Exchange Information Store service in the Services snap-in even if you are in a cluster environment.
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.
Great article that explains the back-end and client setup for entourage and Exchange Server 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
Using exchange 2007 powershell and Excel 2007 to send automated emails of user mailbox stats.
We are trying to get our users mailbox sizes down below 200 MB in anticipation of moving the mailboxes to a new email environment hosted by our parent company. The company I work for currently has over 1500 mailboxes with no current storage limits so the task is going to be somewhat daunting to say the least. I have been given the directive to come up with an automated way of sending each user their mailbox statistics via a personalized email on a weekly basis until the move. I decided to use the exchange powershell and Excel 2007 to accomplish this task and below are the two scripts I used to accomplish it.
First, the Exchange 2007 Powershell script:
#create the output file
#$file = new-item -itemtype file mbstats.csv -force
#create object of mailboxes
$colMailboxes = get-mailbox -resultsize unlimited
$strHeaders = “Display Name, Primary SMTP Address, Database, Department, Total Items, Mailbox Size (MB)”
write-output $strHeaders
foreach ($objMailbox in $colMailboxes) {
$mailboxStats = get-mailboxstatistics -identity $objMailbox.alias
if(!$?){
$foreach.movenext()}
else{
$strOutput = $objMailbox.DisplayName + “,” + $objMailbox.PrimarySMTPAddress + “,” + $mailboxStats.DatabaseName + “,” + $objMailbox.office + “,” + $mailboxStats.ItemCount + “,” + $mailboxStats.TotalItemSize.value.toMB()
write-output $strOutput}
}
The above script will export the mailbox stats and put them into a csv file.
Copy and Paste the above code into notepad and save the file with a ps1 extension.
Open the exchange powershell and run the script by typing the name of the ps1 file with | out-file “C:\nameofcsvfile.csv” appended to the end.
For example:
mbstats.ps1 | out-file c:\mbstats.csv
Once the csv file is created, open the csv file with excel, format the file the way you want, and save the file as an excel spreadsheet. (or..write a Macro that does this for you)
Next, the VBA code to loop the file and email people over the 200 MB limit:
Sub SendEmails()
Dim mlNewMessage As MailItem
Dim myOlApp
Dim strBody As String
Dim strFName As String
Dim strItems As String
Dim strMBSize As String
‘Loop through the spreadsheet until the end
Do Until Range(”A2″).Offset(a, 0) = “”
If (Range(”A2″).Offset(a, 4).Value >= 200) Then ‘Checks for mailbox size
strDear = Range(”A2″).Offset(a, 0).Value ‘Start Point
strItems = Range(”A2″).Offset(a, 3).Value ‘Pulls MB Items
strMBSize = Range(”A2″).Offset(a, 4).Value & ” MB” ‘Pulls MB Size
‘Builds Email Body
strBody = “You are being notified because your email storage is currently ” & strMBSize _
& ” which exceeds the new capacity of 200 MB set forth by CompanyName.” & vbCrLf & vbCrLf _
& “Your total mailbox size must be below 200 MB and it is currently above this number.” & vbCrLf & vbCrLf _
& “Please contact the technical support at YourNumber or YourEmailAddress” _
& “if you need help cleaning out or archiving your items.” & vbCrLf & vbCrLf _
& “Thank you,” & vbCrLf & vbCrLf _
& “Your Name” & vbCrLf _ ‘Signature
& “Your Number” & vbCrLf _ ‘Signature
& “Your Email Address” ‘ Signature
strDear = Left(strDear, InStr(1, strDear, ” “, vbTextCompare)) ‘Pulls First Name from Full Name
Set myOlApp = CreateObject(”Outlook.Application”) ‘Create New Outlook Item
Set mlNewMessage = myOlApp.CreateItem(olMailItem) ‘Create New Mail Item
‘Defines Email Body
mlNewMessage.Body = strDear & “,” & vbCrLf & vbCrLf _
& strBody
mlNewMessage.Subject = “Harry Norman mailbox over the size limit” ‘Defines Subject
mlNewMessage.To = Range(”A2″).Offset(a, 1) ‘Defines To
mlNewMessage.Send ‘Sends Email Message
Set myOlApp = Nothing ‘Clears mlOlApp Variable
Set mlNewMessage = Nothing ‘Clears mlOlApp Variable
a = a + 1 ‘Moves to Next Record
Else
a = a + 1 ‘Next Record
End If
Loop
End Sub
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.
Recently one of our sales offices was not able to download postage using their Pitney Bowes postage machine. I was seeing dropped packets from the machine in our Checkpoint firewall logs. The logs were stating that SmartDefense was blocking the packets due to an illegal header format detected in the http protocol.
After speaking with the Pitney Bowes technician it was discovered that the machine uses chunked encoding to transmit the sensitive account information to their servers.
It turns out the SmartDefense isn’t so smart after all. Setting all the HTTP Protocol Inspection pieces of SmartDefense to Inactive didn’t solve the packets being dropped. In order, to fix this issue I had to set all the HTTP Protocol Inspection pieces of SmartDefense to active and check the monitor only checkbox so as not to actually block the packets. This in theory would have shown me exactly the SmartDefense rule that had been blocking the transmissions….not the case. It did allow the chunked encoded packet transmissions to pass through the firewall but it didn’t show me what SmartDefense rule was triggering the block. On to trial and error…..
Finally, I figured out that in order to fix this issue you must have ASCII Only Response Headers set to active (either active/monitor only or just active). This will allow the chunked encoded packets through the firewall or at least it has worked for my application. You can find this setting by going into SmartCenter, under the SmartDefense tab > expand Web Intelligence > HTTP Protocol Inspection > set ASCII Only Response Headers to active. You must re-install the policy after making these changes.
We are running Checkpoint NGX R65.
I hope this helps.
Will
A year or so ago I was in need of a USB storage device and found a 2GB Sandisk Cruzer on sale at Office Depot for $29.99 (a deal at the time). At that time I didn’t realize the drive I had just bought was U3 compatible. A short time after plugging the drive into my laptop and seeing the U3 launchpad, my curiosity took over. After a few minutes, I became keenly aware of the possibilities this U3/USB technology brought to my disposal.
The U3 compatible USB drives allow you to install U3 compatible programs directly to the USB drive. There is a whole array of popular programs like Firefox, Thunderbird, Avast! antivirus, password lockers, etc. that you can install on the USB drive and use from any computer without installing them on the computer itself.
Society is becoming ever more dependent on email as a main source of communications, especially in the workplace. One of my biggest challenges is managing all of these emails without spending an inordinate amount of time filing, archiving, searching, etc. for the emails that are important to my job. A friend and colleague of mine, Brian Bohanon, recently turned me on to a very useful Outlook add-in called Xobni.
If you are someone who would like an easy way to manage your email and attachments download this FREE add-in and you will not be disappointed.