Justin's Tech Blog

[PS] C:\>Get-MailboxCalendarSettings ResourceName |fl AutomateProcessing                  : AutoAccept AllowConflicts                      : False BookingWindowInDays                 : 180 MaximumDurationInMinutes            : 0 AllowRecurringMeetings              : True EnforceSchedulingHorizon            : True ScheduleOnlyDuringWorkHours         : False ConflictPercentageAllowed           : 0 MaximumConflictInstances            : 0 ForwardRequestsToDelegates          : True DeleteAttachments                   : True DeleteComments                      : True RemovePrivateProperty               : True DeleteSubject                       : True DisableReminders                    : True AddOrganizerToSubject               : True DeleteNonCalendarItems              : True TentativePendingApproval            : True EnableResponseDetails               : True OrganizerInfo                       : True ResourceDelegates                   : {} RequestOutOfPolicy                  : All

Resolution 4 Try using the command line FTP utility and specify the FTP username in DOMAIN\Username format when you log into the FTP Site. If this works, then you can either instruct all users to log on by using DOMAIN\Username format, or you can specify the default authentication domain that the FTP Service should use when authenticating accounts that do not exist locally and that were not entered in the DOMAIN\Username format. To do this you must make changes to the Metabase. To specify a default logon domain so users do not have to type DOMAIN\Username when logging on to the FTP Server, you can either use the Windows Script Host (if it was installed during the Windows NT Option Pack setup) or the NTOP utility Mdutil.exe. Both methods are described below. To use the Windows Script Host method, use one of the following methods depending on the version of IIS that you are running: Note In IIS 6.0, you can resolve this issue by modifying the metabase only when the FTP isolation typ

Here’s some instructions for updating staff computers to the latest version of JRE using Microsoft System Center Configuration Manager 2007. These steps will allow you to silently deploy JRE and then I’ll cover how to disable automatic updates so users aren’t prompted when a new version is available. 1) First download the latest version of JRE http://www.java.com 2) You’ll get an .exe file, but you can get the .msi file by launching the .exe.  When the installation wizard starts, click next to start the download and when the program starts the actual installation navigate to the LocalAppData folder.  On Windows 7 this is located at C:\Users\<user>\AppData\LocalLow\Sun\Java\jre1.6.0_<version>\ 3) Copy the .msi file to your desktop before installation completes, otherwise the file will be automatically removed 4) On your SCCM server setup your software distribution package according to your environment.  As far as program parameters, make sure you specify the /qn switch for a

  Verify currently what domain controllers hold what roles? C:\> netdom query fsmo Schema owner NS1.test.dom Domain role owner NS1.test.dom PDC role NS1.test.dom RID pool manager NS1.test.dom Infrastructure owner NS1.test.dom Now we'll transfer the roles using NTDSUTIL (you connect to the target server - the one that will hold the roles after the transfer): C:\>ntdsutil ntdsutil: roles fsmo maintenance: connections server connections: connect to server NS2 Binding to NS2 ... Connected to NS2 using credentials of locally logged on user. server connections: quit fsmo maintenance: transfer schema master fsmo maintenance: transfer naming master fsmo maintenance: transfer rid master fsmo maintenance: transfer infrastructure master fsmo maintenance: transfer pdc Note: for the "domain naming master", you may have to type "transfer naming master" only (without "domain") if running the command on a W2K8 DC. Let's get out of here: fsmo mai

Microsoft Outlook lets you configure a delegate for a Microsoft Exchange Server 5.5, Microsoft Exchange 2000 Server, or Microsoft Exchange Server 2003 mailbox. If the delegate that you select is damaged, corrupted, or missing, the following symptoms may occur: Meeting requests are incorrectly sent to previously-removed delegates. You cannot add a user as a delegate if that user was previously a delegate and then had been removed from the list of delegates. A non-delivery report (NDR) is generated when a user sends a meeting request to a mailbox because that mailbox has a delegate whose mailbox has been deleted. The NDR will look similar to the following: Your message did not reach some or all of the intended recipients. The following recipient(s) could not be reached: User D on 4/4/2005 12:10 PM The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the corre

Get-Mailbox -resultsize unlimited | Where {$_.GrantSendOnBehalfTo -ne $null} | select Name, @{Name='GrantSendOnBehalfTo';Expression={[string]::join(";", ($_.GrantSendOnBehalfTo))}} | Export-CSV C:\SendOnBehalfTo.csv –noTypeInformation Let’s break this command down.  The first portion Get-Mailbox -resultsize unlimited retrieves all user mailboxes and doesn’t limit to 1000 as is default with Exchange 2007.  We pipe this command into the next one with the ‘|’ symbol.  Here we use a conditional Where and select the attribute GrantSendOnBehalfTo returning only mailboxes from the first part of the command where said attribute is NOT null or empty. Next, out of these mailboxes that don’t have the GrantSendOnBehalfTo attribute as empty, we select the Name of the user.  Now we should be able to stop here, however, we’re working with a string attribute here and returning Name will return a Multivalued property instead of the proper DN or user name we’re looking for (som

  Get-Mailbox | Where {$_.ForwardingAddress -ne $null} | Select Name, ForwardingAddress, DeliverToMailboxAndForward   Ref: http://exchangeshare.wordpress.com/2008/05/26/faq-find-all-users-with-forwarding-address-is-set/