Justin's Tech Blog

Situation: When we try to modify Dynamic Distribution Group, below message is shown in “Filter” tab: “The Dynamic Distribution Group was created with the Exchange Management Shell. You can use the Exchange Management Shell to modify the filter." Solution: Edit the specific Dynamic Distribution Group in ADSIEdit, change the following value from 1 to 2: Attribute: msExchQueryFilterMetadata Old value: Microsoft.Exchange12.8f91d340bc0c47e4b4058a479602f94c:RecipientFilterType=1 New value: Microsoft.Exchange12.8f91d340bc0c47e4b4058a479602f94c:RecipientFilterType=2 (Note: The attribute after Microsoft.Exchange is variable) Ref: http://blog.craigirvinsworld.com/2010/04/unable-to-modify-exchange-2007-dynamic.html

http://technet.microsoft.com/en-us/library/bb310789(EXCHG.80).aspx http://blogs.technet.com/b/exchange/archive/2007/06/25/3403244.aspx View permissions: Get-PublicFolderClientPermission -Identity "\root folder\sub1\PublicFolder" |format-list Set permissions: Add-PublicFolderClientPermission -Identity "\Rootfolder\sub1\Public folder" -AccessRights PublishingEditor -User "global group" -Confirm –WhatIf Syntaxes [PS] C:\>Get-help Get-PublicFolderClientPermission -examples NAME     Get-PublicFolderClientPermission SYNOPSIS     Use the Get-PublicFolderClientPermission cmdlet to retrieve the user permis     sions for a public folder.       Get-PublicFolderClientPermission "\My Public Folder"     Get-PublicFolderClientPermission -Identity "\My Public Folder" -User Chris     -Server "My Server" | Format-List   Add-PublicFolderClientPermission SYNTAX     Add-PublicFolderClientPermission -Identity <PublicFolderIdPara

Symptoms: A Windows Server 2003-based computer stops responding when you shut down the computer in a remote console session. This problem occurs randomly. Solution: http://support.microsoft.com/?scid=kb%3Ben-us%3B930045&x=16&y=8

psexec \\server cmd /c dir

Recently I heard a interviewer asked this question: You install a hotfix in a Windows server, after the installation, the server reboots with BSOD and unable to boot into Windows, not able to boot in safe mode also. What will be your approach to fix this issue? Honestly, I didn't encounter this situation. As my working knowledge of resolving dead (corrupted) servers,  not to waste much time and resources, if feasible, the best option would be repair Windows, 2nd would be reinstall the OS. This is not the best solution for all indeed. So below is the one I found while googling: Hadn't a chance to give a try, let me see my luck in my next patching cycle :)

[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