Archive for Tips
Giving one user access to another’s mailbox via PowerShell
Posted by: | CommentsThere are plenty of reasons why you might want to give one user access to another user’s mailbox. The first user may be in the hospital, or under HR review, or maybe they’ve been dropping the ball lately and management need to make sure that certain projects have been followed up on. It’s not really our job to care. The fact is, Bill in management has requested that you give Paul Stanley access to Gene Simmon’s mailbox, and for various reasons, logging on to Gene’s mailbox to set these permissions up is not a good option. For one, you’d only be able to delegate access to certain primary folders, not to the whole mailbox, and second, you’d have to know Gene’s password to do that. Because you are a smart admin, you tell Bill you can take care of it easily from the server. And here’s how you do it with Exchange 2007 or Exchange 2010:
Using this powershell command, you can give one user the permission to open and view another user’s entire mailbox. They won’t be able to send mail from that mailbox though, unless you add the SendAs permission:
Add-MailboxPermission user1 -User user2 -AccessRights fullaccess
So if you wanted to give Paul Stanley access to Gene Simmons’ mailbox, you would do this:
Add-MailboxPermission gsimmons -user pstanley -AccessRights fullaccess
To add sending functionality, you would do this:
Add-MailboxPermission gsimmons -User pstanley -AccessRights sendas
Make sure you run the Exchange Management Shell as Admin (escalated) or you may not get the results you were expecting.
If you want to verify the permissions you’ve given Paul, you can run this command:
Get-MailboxPermission gsimmons -User pstanley | fl
After you tell Bill that you’ve taken care of it, he asks you what Paul is supposed to do to view the mailbox. You send him the following instructions:
In Outlook, go into Tools -> Account Settingss and open up the properties on your Exchange email account. Choose More Settings, and when you get to the tabbed window, choose the Advanced tab.
On the Advanced tab, you will see the option to open additional mailboxes. Click Add and type the name of the user whose mailbox you want to open. In this case, Paul could type “Gene Simmons” or “gsimmons”. OK all the way out, and you should see another root mailbox for Gene Simmons added to Paul’s Outlook.
And yes, this can be done in the Exchange Management Console, but PowerShell is quicker!
Setting the Maximum Memory Usage on the Sharepoint Database
Posted by: | CommentsOur earlier post referred to setting the maximum memory usage for the SBSMonitoring database, but it is not the only default database that can use a large amount of RAM. The Sharepoint database for the companyweb interface can also get a bit out of control at times. Here are the steps to limit the maximum amount of RAM used:
- On the SBS 2008 server, open the Start menu and select All Programs.
- Select Microsoft SQL Server 2005.
- Right-Click on SQL Server Management Studio Express and select Run As Administrator. If you don’t run the tool as Administrator, the remaining steps will not work.
- Enter the following for the datbase name:
\\.\pipe\mssql$microsoft##ssee\sql\query - Click Connect.
- When the Object Explorer window opens, right-click on the top item (\\.\pipe\mssql$microsoft##ssee\sql\query) and select Properties.
- Click on the Memory page in the left-hand column.
- Change the Maximum Server Memory value to something a little more reasonable. The minimum RAM is set to 128, so the maximum cannot be set lower than that. You may need to tweak this value to ensure proper performance out of the Sharepoint database.
- Click OK and the database memory usage will be adjusted.
- Close SQL Server Management Studio Express when finished.
Want to see this in action? Check out our screencast of the process!
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support
Blog
Twitter
Facebook
LinkedINSetting the Maximum Memory Usage on SBSMonitoring
Posted by: | CommentsSusan Bradley had an often-referenced post on how to adjust the maximum memory usage of the SBSMonitoring MSDE instance in SBS 2003. Surprise, the SBSMonitoring database in SBS 2008 can also grow exceedingly large if not kept in check. The memory limits for the SBSMonitoring database can be adjusted in the SQL 2005 Management Studio Express on an SBS 2008 server. Here are the steps to do that:
- On the SBS 2008 server, open the Start menu and select All Programs.
- Select Microsoft SQL Server 2005.
- Right-Click on SQL Server Management Studio Express and select Run As Administrator. If you don’t run the tool as Administrator, the remaining steps will not work.
- Select the database from the drop-down list, or enter it as servername\SBSMONITORING, then click Connect.
- When the Object Explorer window opens, right-click on the top item (servername\SBSMONITORING) and select Properties.
- Click on the Memory page in the left-hand column.
- Change the Maximum Server Memory value to something a little more reasonable (100 has been bantered around as a reasonable value, but you may need to adjust depending on the server performance).
- Click OK and the database memory usage will be adjusted.
- Close SQL Server Management Studio Express when finished.
Want to see this in action? Check out our screencast of the process!
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support
Blog
Twitter
Facebook
LinkedINAdding IPv6 to DNS
Posted by: | CommentsThis weekend I noticed that NSLOOKUP on my SBS 2008 server is no longer able to return the local DNS server name. Maybe it’s just semantics because otherwise NSLOOKUP seems to work fine, just was bothering me. Having noticed that it is using the IPv6 address for NSLOOKUP resolution I knew right away what the problem was – there’s no IPv6 information in my DNS. Specifically NSLOOKUP uses the PTR record.
Here’s how to resolve that problem:
At this point we’re just using a LinkLocal IP address. All LinkLocal addresses start with the prefix fe80:: Which in ipv4 speak is like the 169.254…addressing. It doesn’t go anywhere, it is just for internal use.
- Create an IPv.6 AAAA host record in the .local zone
2. Create an IPv.6 reverse lookup zone for fe80::/64
3. Create a ptr record for the IPv6 address of the server. To do this use the browse option in the new PTR record window
Now NSLookup will know the name of the local DNS server.
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support
Blog
Twitter
Facebook
LinkedIN
Avoiding Trouble with Windows Updates
Posted by: | CommentsDo you ever wonder why there are so many sporadic one-off problems with Windows Update? Someone runs a .Net update and it breaks a lot of things, even though thousands of other admins have run that same patch without problems?
I think I might have an inkling why.
How many times have you been checking on a server right before lunch and saw an optimization you could easily make, made the change and then saw that the server wanted a reboot? It wasn’t that critical a change, and you can’t restart the system during business hours, so you add a task to your list to restart the server that evening. Or do you? Did you ever actually get around to it?
Maybe you download a patch for a known issue and then it calls for a reboot, and you decide that you might as well run some other updates before the reboot to get your downtime’s worth.
Both of these situations are much more likely to result in failed Windows Updates, since there are unresolved .dll, file and registry changes underway.
The best practice is to restart a server BEFORE you run Windows Update or any significant patches. You would do this in order to ensure that there are no subsystems that can’t be patched properly due to their already holding their breath for a reboot. So a good Windows Update procedure would involve at least two server restarts: one before the updates are run, and another after.
The truth is, if your servers run for 30+ days between reboots, it’s fairly common for them to begin to accumulate some of these “pending reboot” situations, and if you don’t resolve those before doing any serious patching, you may end up with unpredictable results.
—
So who wrote this blog and what do they do for a living anyway?
We’re Third Tier. We provide advanced Third Tier support for IT Professionals.
Get Support
Blog
Twitter
Facebook
LinkedIN

