Manager can update membership list (multiple users)

The add-adpermission method is such a more elegant fix than what other bloggers have. Good post!

Alwin Perotti's Blog

If you need to give a user permission to update active directory security or distribution group members you need to give the user write permission on the active directory group object. After one of the following actions a user is able to update the members of a group with Microsoft Outlook of Active Directory Users and Computers.

  1. Active Directory Users and Computers (one user only)
    Check “Manager can update membership list” checkbox for AD groups
  2. With Tools4ever’s UMRA (for multiple users)
    – Use the “Add AD permissions” Dynamic Action
    – Use the following fields
      – Idenity
      – Account
      – Access rights = “WriteProperty”
      – Properties = “Member”
      – DomainController
     
  3. Microsoft Exchange Powershell SnapIn (for multiple users)
    Add-ADPermission -Identity ‘AD_Group_Name’ -User ‘AD_Username’ -AccessRights WriteProperty -Properties “Member”

Group

View original post

Exchange 2010 Set-WebServicesVirtualDirectory error: Unable to access the configuration system on the remote server

Problem:

When trying to run the Exchange powershell command Set-WebServicesVirtualDirectory the following error is returned:

Unable to access the configuration system on the remote server

Solution:

The fix is to re-register the application pool using the aspnet_regiis command (http://msdn.microsoft.com/en-us/library/k6h9cz8h(v=vs.140).aspx)

Identify if the application pool uses 32 bit or 64 bit by opening Task Manager, the w3wp.exe will show *32 next to the image name if the w3wp is running in 32-bit mode, if no *32 is shown next to the image name, then the worker process is running in 64-bit mode.

  • From the command prompt,
    • If its  V2.0 32 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework\v2.0.50727
    • If its V2.0 64 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v2.0.50727
    • If its V4.0 32 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v4.0.30319
    • If its V4.0 64 bit .Net 2.0 Framework then traverse to C:\windows\microsoft.net\framework64\v4.0.30319
  • Then run the command aspnet_regiis -config+

Root Cause:

So why was it necessary to run this command at all? The Exchange Server was upgraded from 2008 R2 to 2012 R2. For several months Exchange ran fine post upgrade without any issue. The issue was only noticed when I tried to run the set-webservicesvirtualdirectory command.

Exchange 2010 New-MailboxExportRequest IncludeFolders Sub-Folders

To export all folders under a folder use following syntax:

new-mailboxexportrequest -mailbox [mailbox] `
-filepath [unc] -IncludeFolders "TestFolder/*"

If you try to export a sub folder, be sure to replace “/” with “//”, for example, if you want export a folder named “SubFolder”:

new-mailboxexportrequest -mailbox [mailbox] `
-filepath [unc] -IncludeFolders "TestFolder\\SubFolder"

And if you want to ensure you have the proper name of a folder to export, this command is handy:

Get-MailboxFolderStatistics -Identity [mailbox] |`
 ft identity

Powershell: Compare 2 Folders and Remove Matching Files

$Folder1 = Get-ChildItem -Path "C:\Folder1" -filter *.txt
$Folder2 = Get-ChildItem -Path "C:\Folder2" -filter *.txt
$FileList = Compare-Object $Folder1 $Folder2 -IncludeEqual -ExcludeDifferent
foreach($i in $filelist){remove-item -path ("C:\Folder1\" + $i.inputobject)}

$filelist is going to contain a list of file names that were found in both Folder1 and Folder2. In this case I wanted to remove the files in Folder1 that were also found in Folder2.

2X ApplicationGateway Printer Redireciton Failing

Error in the 2X log:

TS Agent hostname: [E 08/00000013] Failed to enum printers (The RPC server is unavailable.   [0x000006ba])

This error is different from the other, more typical errors related to printer redirection where the driver is missing. This error is inidicating a problem with the 2X Universal Printer driver.

Running a repair install of the Universal Printer driver resolved this problem.

C:\Program Files\2X\ApplicationServer\UniversalPrinter\x64>2XUnivPrnInst.exe /R