Exchange 2007, PowerShell
Theses are the PowerShell commands which I have found useful when managing resource mailboxes.
Add-mailboxPermission
-user: choose the user
-access rights : assign the rights (typically FullAccess)
Add-AdPermission
-ExtendedRights Send-As: to add send as permissions.
Set-Mailbox
-GrantSendOnBehalfTo : to add send on behalf of permission. This takes Display Name.
Set-MailboxCalendarSettings
-ResourceDelegates: set up delegates to receive copies. Uses Display Name not account name. Need to specify all delegates, as this overwrites current settings.
Friday, 22 October 2010
Monday, 18 October 2010
Condeco Missing User
Could not book in a user to a meeting room in Condeco.
It was discovered that the user did not exist in the Condeco system, so asked her to log in with her active directory credentials.
She logged on, and was then created as a user in Condeco.
However it was still not possible to make a booking under her name.
In active directory, the user did not have a firstname and lastname set. After setting the firstname and lastname (and waiting for replication) it became possible to book a meeting room for the user.
Condeco is searching active directory on the firstname and lastname fields, even although the user exists with this data in Condeco, it still searches active directory when trying to set a user to host a meeting.
It was discovered that the user did not exist in the Condeco system, so asked her to log in with her active directory credentials.
She logged on, and was then created as a user in Condeco.
However it was still not possible to make a booking under her name.
In active directory, the user did not have a firstname and lastname set. After setting the firstname and lastname (and waiting for replication) it became possible to book a meeting room for the user.
Condeco is searching active directory on the firstname and lastname fields, even although the user exists with this data in Condeco, it still searches active directory when trying to set a user to host a meeting.
Tuesday, 12 October 2010
Powerpoint crashes with "sdt1c.dll" and "Kernel32.dll" errors
Windows XP 32Bit
Powerpoint 2007
Powerpoint crashing either on start up or when trying to print. The guilty file being either kernel32.dll or sdt1c.dll. Repair and reinstall not useful.
Further investigation reveals that sdt1c.dll is a Dell printer driver file. Tried removing this Dell printer and now Powerpoint works without trouble.
Reinstall the printer with the latest drivers downloaded from Dell website.
Powerpoint 2007
Powerpoint crashing either on start up or when trying to print. The guilty file being either kernel32.dll or sdt1c.dll. Repair and reinstall not useful.
Further investigation reveals that sdt1c.dll is a Dell printer driver file. Tried removing this Dell printer and now Powerpoint works without trouble.
Reinstall the printer with the latest drivers downloaded from Dell website.
Monday, 11 October 2010
Group policy fail
Windows XP machine on the domain receiving the message "Cannot connect to admin.root.com" (Server Down) group policy processing aborted.
These machines can not ping the admin.root.com domain for some reason
nslookup will not find admin.root.com... nslookup with a different DNS server will find admin.root.com.
So it appears to be a DNS issue... but other computers on the domain are not receiving the same error, using the same DNS servers.
Removed machine from domain, ran newsid and rejoined domain - no luck.
These machines can not ping the admin.root.com domain for some reason
nslookup will not find admin.root.com... nslookup with a different DNS server will find admin.root.com.
So it appears to be a DNS issue... but other computers on the domain are not receiving the same error, using the same DNS servers.
Removed machine from domain, ran newsid and rejoined domain - no luck.
Monday, 4 October 2010
Duplicating Meeting Requests - Outlook 2007
Outlook 2007
User A has been set up as a delegate of User B. User A also has access to User B's mailbox.
If user A creates a new meeting request they must accept the request from their own mailbox, and not from user B's mailbox. In the event that user A accepts from user B's mailbox, the meeting will be duplicated in user B's calendar, one accepted and the other pending. This is because the invite is copied to user A and not deleted if user A accepts it using their own credentials.
If user A accepts from their own mailbox Outlook recognises they are a delegate and removes the request from user B's mailbox as well.
User A has been set up as a delegate of User B. User A also has access to User B's mailbox.
If user A creates a new meeting request they must accept the request from their own mailbox, and not from user B's mailbox. In the event that user A accepts from user B's mailbox, the meeting will be duplicated in user B's calendar, one accepted and the other pending. This is because the invite is copied to user A and not deleted if user A accepts it using their own credentials.
If user A accepts from their own mailbox Outlook recognises they are a delegate and removes the request from user B's mailbox as well.
Enabling Unified Messaging for users
Exchange Server 2007
To enable unified messaging, simply right click from Exchange Management Console, and select to enable from the context menu.
Select an appropriate policy for the user. Policies can be viewed or created from unified messaging under the Organization configuration. Having Exchange generate the user PIN will keep this information secure. The user will receive a mail with a random 4 digit PIN.
The user must have a telephone number in the exchange properties "address and phone" tab in order to automatically populate the extension field.
To enable unified messaging, simply right click from Exchange Management Console, and select to enable from the context menu.
Select an appropriate policy for the user. Policies can be viewed or created from unified messaging under the Organization configuration. Having Exchange generate the user PIN will keep this information secure. The user will receive a mail with a random 4 digit PIN.
The user must have a telephone number in the exchange properties "address and phone" tab in order to automatically populate the extension field.
Subscribe to:
Posts (Atom)