|
|
Browse by Tags
All Tags » devmsgteam » Powershell (RSS)
Showing page 1 of 4 (34 total posts)
-
As we know by default the Display Name of Exchange Mailboxes(Exchange Server 2007 SP2) is in the format of “Firstname Lastname”. I want to change this for the couple of existing mailboxes to “Lastname, Firstname” for one my customer – he preferred non-development stuff!! I tried to do the same using the Exchange Management Shell, which fits for my requirement: > Get-Mailbox “User Name” | Get-User | ?{ $_.Lastname -ne $null } | %{ $dispName=$_.LastName + “, ” + $_.FirstName ; set-mailbox $_.SamAccountName
Posted to Le Café Central de DeVa (Weblog) by deva on September 30, 2009
Filed under: Exchange Server 2007, cmdlet, Powershell, Exchange Management Shell (EMS), mailbox, DevMSGTeam, Exchange Programming
-
We can use following Exchange PowerShell cmdlet to grant a Service Account full access to all the mailboxes on Exchange Server 2007 mailboxstore, but do so only in accordance with your organization's security and privacy policies: Get -mailboxserver <servername> | add-adpermission –user <service account> -accessrights GenericRead, GenericWrite -extendedrights Send- As , Receive- As , ms-Exch-Store-Admin .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas,
-
With continuation of my previous article , it just points out to find how we can get by using UI(User Interface like snap-in, MMC Console, ESM..etc)’s. This time, let me try something different with Exchange Server 2007 (i tried with Exchange Server 2007 SP1 RUx) with its powershell/cmdlet. In order to get the version number, i tried like this to obtain the attributes of the server, > Get-ExchangeServer | Select ExchangeVersion, AdminDisplayVersion This provides the ExchangeVersion and AdminDisplayVersion
Posted to Le Café Central de DeVa (Weblog) by deva on July 29, 2009
Filed under: Exchange Server 2007, cmdlet, Powershell, Exchange Management Shell (EMS), How to, DevMSGTeam, development, Exchange Programming, Service Pack, Build, version
-
Redistribution of files in the “ C:\Program Files\Microsoft\Exchange Server ” folder and sub-folders is not advised/supported. Yes, this does include the “C:\Program Files\Microsoft\Exchange Server\Public” folder also. These files are installed when the Exchange 2007 (or later) tools are installed. If you need these files with the minimal installation, then use the Exchange installer to install them – the box will need to be at least in an Exchange Admin role. There is no installer/redistributable
Posted to Dan's WebDAV 101 (Weblog) by danba on April 2, 2009
Filed under: Microsoft.Exchange.Data.dll, powershell, Microsoft.Exchange.Data.Directory.dll, HOWTO, Exchange, Exchange 2007, 2007, mime, distribution, DevMsgTeam, installer, multivalve, C:\Program Files\Microsoft\Exchange Server, installation, transport agent, Microsoft.Exchange.Data.ContentTypes.dll, eula, redistribution
-
This is my first attempt to write a Powershell sample to my readers. In this sample we will give Send-As, Receive-As, ms-Exch-Store-Admin rights to an active directory user. We will be piping two commands here… Get-MailboxServer and the result will go to Add-AdPermission. You may give same permissions using Exchange Power Shell Window C:\>Get-MailboxServer –Identity MSGEX07 | Add-AdPermission –User UserA –AccessRights GenericRead, GenericWrite –ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin
Posted to Jive into Messaging world (Weblog) by Vikas Verma on March 30, 2009
Filed under: Exchange 2007, CmdLet, HOWTO, Powershell, Samples, DevMsgTeam, Add-AdPermission, PSSnapInException, CreatePipeline, StringBuilder, CreateRunspace, Get-MailboxServer
-
The other day I was working on a case where the customer was using VBScript and CDO 1.21 to make some changes in some mailboxes, and I couldn’t help but feel that we were working in the past. Don’t get me wrong, there’s a lot of tried and tested VBScript and CDO 1.21 code out there, but I found myself wondering what the “new” way to do this would be. I started looking at using Powershell to automate a .Net HttpWebRequest to post to an EWS endpoint, and just build the SOAP requests myself (or leverage
-
With the continuation of the previous blogpost , today we’re going to see how we can use Microsoft Office Outlook Web Access or the Exchange Management Shell to configure language settings for Outlook Web Access in Microsoft Exchange Server 2007. Microsoft have provided various options to customize the OWA pages, contents/images/themes in a simpler way. As a part of that, we cam make sure that we can do the language setting for OWA, which determines the language of the Outlook Web Access logon page
Posted to Le Café Central de DeVa (Weblog) by deva on March 2, 2009
Filed under: Locale, Exchange Server 2007, Best Practices, cmdlet, Powershell, Exchange Management Shell (EMS), API Changes, Support Guidelines, Configure, mailbox, Errors, Customization, DevMSGTeam, development, OWA, Client Access Server (CAS), Forms Based Authentication, logon, identity, bulk, Language, Regional Settings
-
The easiest solution is to create a COM component and register that component with component services (COM+) running the component under a specific user identity. Why do I say this? Read on... In my case the Web site/Application was configured to run under the DefaultAppPool (Identity = Network Service) and you I wanted to use PowerShell to Enable a Mailbox on Exchange 2007. The code is running on the Exchange 2007 Server itself . What are the available options? 1) Impersonate the user who has the
-
In this session, we will have a look about how to get the mailbox statistics information using from Exchange Server 2007 SP1 using C#.Net & Exchange Powershell. I tried the following code to get the mailbox statistics… 1: .... 2: //Create Runspaceconfiguraiton object 3: RunspaceConfiguration config = RunspaceConfiguration.Create(); 4: PSSnapInException snapEx = null ; 5: 6: //Add it to the Powershell SnapIn 7: PSSnapInInfo info = config.AddPSSnapIn( "Microsoft.Exchange.Management.PowerShell.Admin"
Posted to Le Café Central de DeVa (Weblog) by deva on December 21, 2008
Filed under: Exchange Web Services (EWS), Exchange Server 2007, Code Snippets, Powershell, Exchange Management Shell (EMS), Configure, mailbox, DevMSGTeam, Programming, development, C#
-
Of course you cannot use WMI to manage Exchange 2007, obviously Powershell is more power full and recommended to be used on Exchange 2007 Server. We will talk about Powershell and how to do same for 2007 later. For now you can use following script to get the statistics data from Exchange WMI Provider and Exchange_Mailbox class of it. On Error Resume Next Const wbemFlagReturnImmediately = &h10 Const wbemFlagForwardOnly = &h20 arrComputers = Array( "Server1" , "Server2"
1
|
|
|