Wednesday, November 16, 2011

Windows 2008 R2 Powershell script error

For security, Windows 2008 R2 won't run PowerShell scripts by default (Disabled). Thus we need to adjust the ExecutionPolicy to allow PowerShell scripts to run. The better method is to issue this instruction at the PowerShell command line:
 
set-ExecutionPolicy RemoteSigned
Posted by at No comments:

Thursday, September 8, 2011

Weak and Strong Host Behavior in Windows for multihomed Computer

Weak and Strong Host Behavior in Windows
Windows XP and Windows Server® 2003 use the weak host model for sends and receives for all IPv4 interfaces and the strong host model for sends and receives for all IPv6 interfaces. You cannot configure this behavior. The Next Generation TCP/IP stack in Windows Vista and Windows Server 2008 supports strong host sends and receives for both IPv4 and IPv6 by default on all interfaces except the Teredo tunneling interface for a Teredo host-specific relay. Figure 4 lists the commands that you can use to configure send and receive behavior for both IPv4 and IPv6 on a per-interface basis. Note that InterfaceNameOrIndex is either the name of the interface from the Network Connections folder or its interface index. You can obtain the interface index of an interface from the display of the command:
 
 Commands to configure strong and weak send and receive behavior
• netsh interface ipv4 set interface [InterfaceNameOrIndex] weakhostsend=enabled|disabled
• netsh interface ipv4 set interface [InterfaceNameOrIndex] weakhostreceive=enabled|disabled
• netsh interface ipv6 set interface [InterfaceNameOrIndex] weakhostsend=enabled|disabled
• netsh interface ipv6 set interface [InterfaceNameOrIndex] weakhostreceive=enabled|disabled
 
netsh interface ipv6 show interface
Reference:
 
 
Posted by at No comments:

Wednesday, September 7, 2011

MailboxServer is partially configured – ExBPA


When running ExBPA against an Exchange 2007 mailbox server, the following error text may be noted:
===========================================================

Error: 'MailboxServer' is partially configured
Server: <SERVER>

'MailboxServer' is partially configured on server <SERVER>.contoso.com. Either setup is configuring it right now or setup failed while configuring it. Please rerun setup if it isn't currently running.


Or if you tried to install some third party application that require mailbox role installed, you may get message that you cannot install the the application since there is no mailnox role installed though you know your mailbox server functions very well


Cause: Once you intially ran Exchange Setup, setup might failed and you fixed the error and installed the mailbox server sucessfully.


Resolution: Make sure your mailbox server role works properly and then using regedit


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\v8.0\MailboxServer]
"Action"="Install"
"Watermark"=REG_SZ:7448a073

"UnpackedVersion"=REG_SZ:8.3.83.6


remove "Watermark"=dword:7448a073


Remove "Action"="Install"


Add


"ConfiguredVersion"=REG_SZ:8.3.83.6


After, we will see


"ConfiguredVersion"=REG_SZ:8.3.83.6

"UnpackedVersion"=REG_SZ:8.3.83.6


your mileage may vary for the version value:


runn ExBPA against the Exchange 2007 mailbox server again, you should be fine.


Reference



Posted by at No comments:

Tuesday, August 16, 2011

Event ID 20280 {user@mycompany.com} DoICS() failed: ERR_FAIL

BES 5.0.3 SP3 MR 2, Exchange 2007 SP3 Rollups4
 
Multiple Instance of Each:
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::CheckSelectedFolders - OpenEntry (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::MAPIAttachtoRIMAttach - OpeProperty (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::MAPIAttachtoRIMAttach - GetAttachmentTable (0x80004005) failed
 
Event ID 20265
{user@mycompany.com} MAPIMailbox::IsMAPIMessageSecureEmail - pMessage -> GetAttachmentTable (0x80004005) failed

Event ID 20530
{user@mycompany.com} ConstructPIMFolder - Failed to open the memo folder for user (0x80004005)
 
Event ID 20529
{user@mycompany.com} ConstructPIMFolder - Failed to open the task folder for user (0x80004005)
 
Event ID 20528
{user@mycompany.com} ConstructPIMFolder - Failed to open the contact folder for user (0x80004005)
 
Event ID 20205
(user@mycompany.com} AddRefIDProp(): ERR_FAIL, EntryId=58(xx) (many incrementing)

Event ID 20280
{user@mycompany.com} DoICS() failed: ERR_FAIL
 
Event ID 20043
CallCSAgent::Sych: Could not reload synchronization state for User12345
 
Event ID 20048
CallCSAgent:: - LoadSyncInfo Create BlackBerryHandheldInfo Folder (0x80004005) failed for User12345
 
Event ID 20048
CallCSAgent:: - SaveSyncInfor Create BlackBerryHandheldInfo Folder (0x80004005) failed for User12345
 
Event ID 20455
{user@mycompany.com} MAPIMailbox::CheckUserOriginatedItem - OpenEntry (0x80004005)failed
 
Event ID 20185
{user@mycompany.com} GetRIMMessage() failed: ERR_FAIL
 
 
 
Solution:
 
remove user from BES
Close Outlook on users machine
run Outlook with /resetfolders switch
Add user back to BES
reactivate device
 
Posted by at No comments:

Friday, July 29, 2011

The Exchange binary files are not installed but the backup registry key is present. Only build-to-build upgrade mode is available.

First, once you applied SP3, it will start check prerequite, then to remove exchange binarnies files, and to install Exchange 2007 SP3 binaries. If your installation failed with corrupt of installation file, say, Exchangeserver.msi file, etc, installation would fail with error and it cannot roll back to previous Exchange build you ran on the server. Once you try to re-apply Exchange 2007 SP3, or reboot your Exchange server and reapply SP3:
 
You Receive a Message That States That Only the Build-Build Upgrade Mode Is Available When You Install Exchange 2007 Service Pack 3
 
 
This topic provides information about how to troubleshoot an installation error that may occur when you try to install Microsoft Exchange Server 2007  Service Pack 3 (SP3).
 
When you run the Setup program to install Exchange Server 2007 SP3, you receive the following error message:

The Exchange binary files are not installed but the backup registry key is present. Only build-to-build upgrade mode is available.
 
Cause
 
This issue may occur if the Exchhelp.chm file is missing from the Exchange Server\Bin folder on the Exchange server.
Resolution
 
To resolve this issue, follow these steps:
  1. Extract the Exchange 2007 SP3 files from the installation package. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. Change to the directory that contains the E2K7SP1En64.exe file.
    3. Type e2k7sp3en64.exe /x, and then press ENTER.
    4. In the Choose Directory For Extracted Files dialog box, type the path where you want to extract the files, and then click OK. For example, type c:\exchange2007sp3files.
    5. When the Extraction Complete message appears, click OK.
  2. Copy the appropriate language version of the Exchhelp.chm file from the location where you extracted the files to the Exchange Server\Bin directory on the Exchange server. For example, copy the C:\Exchange2007sp3\Setup\Serverroles\Common\mui\0409\Exchhelp.chm file to the %ProgramFiles%\Exchange Server\Bin directory.
  3. Verify that the following services are set to an Automatic startup type and that the services are started:
    • IIS Admin Service (IISADMIN)
    • HTTP SSL (HTTPFilter)
      Note   This service is not present on a Windows Server 2008-based computer.
    • World Wide Web Publishing Service (W3SVC)
  4. Verify that all the Exchange-related services are set to an Automatic startup type and that the services are started.
  5. Start the Exchange 2007 SP3 installation from a command-line, and specify the upgrade option. To do this, follow these steps:
    1. Click Start, click Run, type cmd, and then click OK.
    2. At the command prompt, move to the directory to which you extracted the Exchange 2007 SP3 installation files. For example, move to the C:\Exchange2007sp1files directory.
    3. Type setup.com /mode:upgrade, and then press ENTER. The Microsoft Exchange Server 2007 Unattended Setup program starts.
Note: The above procedures tested OK in LAB even if you remove all Exchange 2007 related services registry keys....
 
 
Posted by at 7 comments:

Send connector Intra-Organization SMTP Send Connector has failed to authenticate with your remote server IP:25. The response from the remote site is 454 4.7.0 Temporary authentication failure

In a Microsoft Exchange Server 2007 environment or in a Microsoft Exchange Server 2010 environment, some e-mail messages are stuck in a remote delivery queue that should have been transferred to another Exchange server in the Exchange organization. If you open the Queue Viewer tool from the Toolbox node on the Exchange Management Console, the Last Error field displays an error message that resembles the following:
 
Send connector Intra-Organization SMTP Send Connector has failed to authenticate with 172.18.102.95:25. The response from the remote site is 454 4.7.0 Temporary authentication failure
 
Event ID: 1035 is logged when some e-mail messages are stuck in a remote delivery queue in a Microsoft Exchange Server 2007 environment or in a Microsoft Exchange Server 2010 environment.
 
Cause: This issue occurs if the Exchange server cannot authenticate with the remote Exchange server. Exchange servers requires authentication to route internal user messages between servers. The issue can be caused by one of the following reasons:
  • The Exchange server is experiencing Time synchronization issues
  • The Exchange server is experiencing Service Principle Name (SPN) issues
  • The required TCP/UDP ports for the Kerberos protocol are blocked by the firewall.
To resolve this issue, follow these steps:
  1. Check the clock on both servers and domain controllers that might be used to authenticate the servers. All clocks should be synchronized to within 5 minutes of one other.
  2. Verify that the Service Principle Name (SPN) for SMTPSVC is registered correctly on the target server.
    • Make sure that the SMTP and SMTPSVC entries are added correctly to the machine account by using the SetSPN tool. For example:
      SetSPN -L <ExchangeServerName>
      SMTP/<ExchangeServerName>
      SMTP/<ExchangeServerName>.example.com
      SMTPSVC/<ExchangeServerName>
      SMTPSVC/<ExchangeServerName>.example.com
    • Check for duplicate SPNs by using the SetSPN tool. There should only be one entry of each:
      SetSPN -x
      Processing entry 0
      found 0 group of duplicate SPNs.
  3. Verify that the ports required for Kerberos are enabled.
  4. If the previous steps do not work, you can turn on logging for Kerberos on the Server that is registering the Event 1035 message, which may provide additional information. To do this, follow these steps:
    1. Click Start, click Run, type Regedit, and then click OK.
    2. Locate the following registry key:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
    3. On the Edit menu, point to New, and then click DWORD Value.
    4. In the details pane, input the new value LogLevel, and then press Enter.
    5. Right-click LogLevel, and then click Modify.
    6. In the Edit DWORD Value dialog box, under Base, click Decimal.
    7. In the Value data box, type the value 1, and then click OK.
    8. Close Registry Editor.
    9. Again check the System Event log for any Kerberos errors.
Please note: Make all Exchange servers and all DCs. All clocks should be synchronized to within 5 minutes of one other.
 
ref:
 
 
Posted by at No comments:

Wednesday, July 20, 2011

How to Reindex Outlook 2007 or later

If you search for items in Microsoft Office Outlook 2007 or later and do not receive the results that you expect, the indexing of your Microsoft Windows and Microsoft Office system data files (the search catalog) may not be complete.
 
Symptoms of an incomplete index include the following:
Partial or no search results are returned.
Items that you expect to appear based on your search criteria are not displayed.
You can rebuild the search catalog, which restarts the indexing of your data files. The search catalog is a file where all of your Outlook and Microsoft Windows items (data files) are indexed. To rebuild your search catalog, do the following:
1.Exit Outlook.
2.In Microsoft Windows, click the Start button, and then click Control Panel.
3.Do one of the following:
 
1) Windows 7 Click Index Option
2) Windows Vista     Click System Maintenance, and then click Indexing Options.
    Note   In Classic view, double-click Indexing Options.
3) Microsoft Windows XP     Under See Also, click Other Control Panel Options, and then click Indexing Options.
    Note   In Classic view, double-click Indexing Options.
4.Click Modify, select the check boxes for the locations you want to index (Outlook), and then click OK.
5.Click Advanced.
6.Click Rebuild.
7.Restart Outlook.
If rebuilding the search catalog does not correct your search problem and retrieve the expected search results, see Instant Search is not finding all the items I expect for additional information.
Posted by at No comments:

Tuesday, July 19, 2011

Cannot delete Default Exchange 2010 Mailbox Database

When an Exchange 2010 mailbox role is installed, a default mailbox database is created. In Exchange 2007, the default database is named "Mailbox Database" whereas in 2010, it comes with a random numbering at the end of the "Mailbox Database" name since you cannot have the same Mailbox Database in your Org with multiple server environments. This is to make the mailbox database name unique. Mine is named "Mailbox Database 0683456784".
 
As most of the admins, your first instinct is to remove the default database and create ones with your company's naming convention or the names of your choice. You created a new database named "MDB1" and tried deleting the default one, only to be greeted with the error below.
 
"This mailbox database contains one or more mailboxes or arbitration mailboxes. Before you can remove this mailbox database, you must disable, move or remove user mailboxes and move arbitration mailboxes"
 
Technet explains arbitration mailboxes as the mailboxes used for managing approval workflow. For example, an arbitration mailbox is used for handling moderated recipients and distribution group membership approval.
 
You moved your user mailboxes to another database and ran the following command to find the arbitration mailboxes.
 
Get-Mailbox –Database "Mailbox Database 0683456784" –arbitration
 
You moved the arbitration mailboxes as well to the second database with the command below.
Get-Mailbox –Database "Mailbox Database 0683456784" –arbitration | New-MoveRequest – TargetDatabase MDB1
You confirmed that the arbitration mailboxes were successfully moved using the
Get-MoveRequest cmdlet.
Once the mailbox move was completed, you could delete your default database!
 
Posted by at No comments:

Friday, June 24, 2011

BES AgentOptimizeAlgorithm

I had been long looking for the feature to distribute agents evening to speed up mailbox scanning processing particular after we upgrade Exchange 2003 to Exchange 2007 a couple years ago. I was always told that sorry we cannot do that by RIM support. Finally I got the postive answer from RIM by editting register key.
 
By default, if you run MSDE, BES only supports two dynamic agents per server. If you run Full MS SQL edition for BES database, you can run as many as 20 agents (RIM recommends you should run less than 10 agents per BES). BES assigns users to agents per Exchange servers and up to 400 users per agent. Since we had migrated all 5000 user mailboxes to one Exchange 2007 CCR server, for about 700 users per BES HA, by default, it will allocate 400 users for two dynamic agents, the message delivery significantly delays whenever we failover BES (it could take about two hours to complete the sync) that made BES failover useless.
 
Now that after we have implemented AgentOptimizeAlgorithm, and changed from two agents to five agents for 800 users per HA server, message delivery delay has been reduced from 2 hours to 15 minutes.
 
Also if you use Exchange 2010, BES basically sees the CAS as the mailbox with 2010 (instead of the actual mailbox server the user is on, assuming you have installed the CAS on a separate server). Because of this, if you have multiple CAS behind a load balancer, it throws the "keep users from the same exchange server on the same BES" rule out. This is our situation and the guidance given to us by RIM is to implement the AgentOptimizeAlgorithm to 1 (simple algorithm) to randomly assign users to an Agent instead of keeping an Agent to one mail server:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
DWORD value is 1 - the simple algorithm is used.
DWORD value is 2 - the complex algorithm is used.
The Default value is 2. a complex algorithm, Note: if you don't see the key, create the REG-Dword key.
 
Enabling Simple Messaging Agent Distribution Algorithm
 
The distribution algorithm can be changed with the DWORD registry key AgentOptimizeAlgorithm located in
32 bit - HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
64bit - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Dispatcher.
DWORD value is 1 - the simple algorithm is used.
DWORD value is 2 - the complex algorithm is used.
The Default value is 2.
 
If the registry key does not exist, create it.
 
No advanced logic is used in this process.
 
BlackBerry smartphone users are simply distributed evenly across the number of agents specified in the DWORD registry key NumAgents located in:
32bit - HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents.
64bit - HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Research In Motion\BlackBerry Enterprise Server\Agents.
Default value is 5, do not increase it higher than 10.
Note: If the above registry keys do not exist, they need to be created.
 
Note: A maximum of 2 Messaging Agents will be created if the configuration database is on Microsoft SQL Database Engine (MSDE).  Move the configuration database to SQL 2005 Express using KB03112.
 
 After talking with RIM on this one, it is my understanding that if you are completely Exchange 2010 or 2007 (instead of mixed mode with 2003) and you have implemented EWS using the traittool on the global level (and not per server or agent) then you can completely uninstall MAPI since it is no longer being used (KEEP CDO THOUGH!). Of course I would test in a lab first, but this is what I intend to do after we are finished migrating to 2010.
 
Note: We run BES 5.0.3 HA with Intel Powerful processors (16 virtual processors with 32 GB RAM)
Posted by at No comments:

"Upgrade Issues" prompt appears when upgrading to BlackBerry Enterprise Server 5.0 SP3 HA

Just done BES 5.02 HA to BES 5.0.3 recently. Since starting from BES 5.0.3 Integrated MDS is no longer support, you may get the following error once you do the upgrade:
 
When upgrading to BlackBerry® Enterprise Server 5.0 SP3, a prompt titled Upgrade Issues may appear that contains wording similar to the following:
The setup application found the BlackBerry MDS Integration Service on the following computers in the BlackBerry Domain:

<ComputerName>

Before you can continue the current upgrade process you must un-install the BlackBerry MDS Integration Service. For more information, see the BlackBerry Enterprise Server Upgrade Guide
 
Cause 1
 
The BlackBerry® Mobile Data System Integration Service (MDS-IS) must be uninstalled from the BlackBerry Domain before an upgrade to BlackBerry Enterprise Server 5.0 SP3 can continue.
Cause 2
 
The BlackBerry Mobile Data System Integration Service (MDS-IS) SQL backup must be deleted from the server so the install of the BlackBerry Enterprise Server 5.0 SP3 can continue.
 
Resolutions:
 
Please choose the appropriate option below and follow the associated steps, depending on the version of the BlackBerry Enterprise Server that is running, or the resolution that fits your circumstances.
The BlackBerry Mobile Data System Integration Service (MDS-IS) must be uninstalled from the BlackBerry Domain before an upgrade to BlackBerry Enterprise Server 5.0 SP3 can continue.
Resolution 1
 
Option - Using CreateDB executable included with BlackBerry Enterprise Server 5.0 SP3
Supported versions:
  • BlackBerry Enterprise Server 4.1 SP7 to 5.0 SP2 MR5 
Related Steps
  1. Extract the BlackBerry Enterprise Server 5.0 SP3 software to a folder.
  2. Navigate to the folder above and double-click the Database folder.
  3. In the Database folder, right-click the BESMgmt.cfg file and choose to open it with Notepad.
  4. In this file, make the following changes:
    1. For CMD=Install, change Install to Upgrade.
    2. For DATABASE_NAME=BESMgmt, replace BESMgmt with the name of your BlackBerry Configuration Database, if different.
    3. For SERVER=local if required, update this value with the name of the Microsoft® SQL Server® that the BlackBerry Configuration Database is hosted on. If an instance is used, specify it as SERVERNAME\INSTANCENAME.
    4. If necessary, populate the MSSQL_PORT= value with the port of your Microsoft SQL Server if different than 1433.
    5. If using Microsoft SQL Server Authentication, populate the USERID= and PASSWORD= values with a Microsoft SQL Server Authentication account that has System Administrator privileges.
    6. Change BACKUP=false to BACKUP=true.
    7. If required, change BES_TYPE=Exchange to Domino if you are running BlackBerry® Enterprise Server for IBM® Lotus® Domino®.
  5. From the menu in Notepad, click File > Save and close the file.
  6. Double-click the CreateDB.exe file in the same folder as the BESMgmt.cfg file.
  7. Proceed with the installation of the BlackBerry Enterprise Server 5.0 SP3 upgrade.

Option - Using installation software and the BlackBerry Administration Service to remove the BlackBerry MDS Integration Service

Supported versions:
  • BlackBerry Enterprise Server 5.0 SP1 to 5.0 SP2 MR5 
Installation Related Steps
  1. Locate or obtain the installation file for BlackBerry Enterprise Server 5.0 SP1 or SP2 and extract it to a folder.
  2. Locate and double-click the Setup.exe file from the above folder.
  3. Choose your language from the drop-down list.
  4. Accept the license agreement and click Next.
  5. Leave all database details as is for your deployment while clicking Next until you reach the Setup Options screen.
  6. On the Setup Options screen, clear the check box beside the BlackBerry MDS Integration Service and click Next.
  7. Click Next, and complete the rest of the setup screens as you would for a new installation.
  8. If prompted, reboot the computer.

    Note: If you are running BlackBerry Enterprise Server 5.0 SP1, skip the steps below and proceed to the BlackBerry Administration Service Steps.
  9. If you don't already have it available, obtain the BlackBerry Enterprise Server 5.0 SP2 MR2 or MR3 software from http://www.blackberry.com/support/downloads.
  10. Extract BlackBerry Enterprise Server 5.0 SP2 MR2 or MR3 software to a folder. Ensure this is a different folder than Step 1 above.
  11. Locate and double-click the Setup.exe file from the folder in Step 10.
  12. Choose your language and click OK.
  13. Click Next.
  14. Enter your service account password and click Next.
  15. Once the installation has completed, reboot the computer.
  16. Click Next on all outstanding prompts for the rest of the installation, leaving all existing options unchanged.
  17. Click Start Services and then click Next.
BlackBerry Administration Service Steps
  1. Once the installation has completed, log in to the BlackBerry Administrative Service.
  2. Under Servers and Components, expand BlackBerry Solution Topology > BlackBerry Domain > Component View> BlackBerry Enterprise Server, and click the server name.
  3. Scroll to the bottom of the resulting page and click Edit Instance.
  4. In the Supported MDS Integration Service instance names, click the drop-down list and select the blank space above the existing entry.
    Click Save All.
  5. Go back to Servers and Components, expand BlackBerry Solution Topology > BlackBerry Domain, and click Component View.
  6. Scroll to the MDS Integration Service heading, and click the Delete icon to delete the instance.
  7. Click Yes - Delete the instance.
  8. When prompted to confirm, click Yes - Delete the instance.
  9. From Windows Services restart the services named BlackBerry Administration Service - Application Server and BlackBerry Administration Service - Native Code Container
Once the above steps are completed, proceed with the upgrade to BlackBerry Enterprise Server 5.0 SP3. Please refer to the Installation Guide for details on completing the upgrade.
Option - Using the installation software and the BlackBerry Manager to remove the BlackBerry MDS Integration Service
Supported versions:
  • BlackBerry Enterprise Server 4.1 SP7
Installation Related Steps
  1. Navigate to Start > Control Panel > Add Remove Programs.
  2. Click the Remove button beside the BlackBerry Enterprise Server.
  3. Click Yes to the resulting prompt that asks if you are sure that you want to remove the software.
  4. If you wish to keep your current logs, click No to the warning about removing them.

    Note: If BlackBerry Manager is installed on a remote computer, there is no need to reinstall the BlackBerry Enterprise Server.  Please proceed to the BlackBerry Manager Related Steps below.
  5. Locate or obtain the full installation file or files used to install or upgrade BlackBerry Enterprise Server 4.1 SP7 software and extract it to a folder.

    Note: If the file that was used to install BlackBerry Enterprise Server 4.1 SP7 has the term upgrader in it, please obtain a full installation file from the BlackBerry Expert Support Center.
  6. Locate and double-click the Setup.exe file from the above folder.
  7. Choose your language from the drop-down list.
  8. Accept the license agreement and click Next.
  9. At the Setup Type screen, select an option that does not include the BlackBerry MDS Integration Service, and click Next.
  10. Click Next at the Preinstallation Checklist screen.
  11. Enter your service account password and the BlackBerry Enterprise Server name (if different from the default populated) and click Next.
  12. Select whether or not you are using a local or remote Microsoft SQL Server and click Next.
  13. Click Next at the Installation Summary screen.
  14. Once the installation is complete, reboot the computer if you are not prompted to do so.
  15. After the reboot, enter database information for your installation and click Next.
    Complete all other prompts that should have pre-existing information present while clicking Next, and then click Start Service, then click Finish.
BlackBerry Manager Related Steps
  1. Open the BlackBerry Manager by navigating to Start > Programs > BlackBerry Enterprise Server, and click BlackBerry Manager.
  2. For each BlackBerry Enterprise Server in the left navigational bar, perform the following:
    1. Select the BlackBerry Enterprise server from the left navigational bar.
    2. On the right pane, click the Server Configuration tab.
    3. In the pane below, click Edit Properties.
    4. In this new window, click MDS Integration Service on the left navigation area.
    5. On the right, click the URL beside BlackBerry MDS Integration Service Server URL, and choose Default.
    6. Click Apply then OK.
  3. Click the BlackBerry Domain icon on the left navigation bar.
  4. On the right, click the drop-down list named Service Control & Customization.
  5. Click the option named Delete MDS Integration Service.
  6. In this new window, select the MDS Integration Service entry and click Remove.
  7. Click Apply, then OK.
Once the above steps are completed, proceed with the upgrade to BlackBerry Enterprise Server 5.0 SP3. Please refer to the Installation Guide for details on completing the upgrade.
The BlackBerry Mobile Data System Integration Service (MDS-IS) SQL backup must be deleted from the server so the install of the BlackBerry Enterprise Server 5.0 SP3 can continue.
Resolution 2
1) Browse to <drive>:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup
2) Delete the MDSIS backup files.
 
Additional Information
The BlackBerry MDS Integration Service is only responsible for facilitating connectivity for BlackBerry MDS Runtime Applications, and has no effect on Internet or intranet browsing, nor other third-party Java® or web applications.
Note: BlackBerry Enterprise Server 5.0 SP2 Maintainance Release 2, 3, 4 or 5 are required to be installed as they fix an issue related to removing the BlackBerry Mobile Data System - Integration Service (MKS762391) when using the BlackBerry Administration Service.
 
Note: We did option 2, we still have the issue. Option1 is the best choice.
Posted by at No comments:

Friday, June 3, 2011

Exchange 2010, say good bye to single instance storage (SIS)

 
 
In Exchange Server 2010, there is no more single instance storage (SIS). To help understand why SIS is gone, let's review a brief history of Exchange.
During the development of Exchange 4.0, we had two primary goals in mind, and SIS was borne out of these goals:
  1. Ensure that messages were delivered as fast and as efficient as possible.
  2. Reduce the amount of disk space required to store messages, as disk capacity was premium.
Exchange 4.0 (and, to a certain extent, Exchange 5.0 and Exchange 5.5) was really designed as a departmental solution. Back then, users were typically placed on an Exchange server based on their organization structure (often, the entire company was on the same server).  Since there was only one mailbox database, we maximized our use of SIS for both message delivery (only store the body and attachments once) and space efficiency. The only time we created another copy within the store was when the user modified their individual instance.
For almost 19 years, the internal Exchange database table structure has remained relatively the same:
Then came Exchange 2000.  In Exchange 2000, we evolved considerably - we moved to SMTP for server-to-server connectivity, we added storage groups, and we increased the maximum number of databases per server.  The result was a shift away from a departmental usage of Exchange to enterprise usage of Exchange.  Moreover, the move to 20 databases reduced SIS effects on space efficiency, as the likelihood that multiple recipients were on the same database decreased.  Similarly, message delivery was improved by our optimizations in transport, so transport no longer benefited as much from SIS either.
With Exchange 2003, consolidation of servers took off in earnest due to features like Cached Exchange Mode.  Again the move away from departmental usage continued.  Many customers moved away from distributing mailboxes based on their organization structure to randomization of the user population across all databases in the organization.  Once again, the space efficiency effects of SIS were further reduced.
In Exchange 2007, we increased the number of databases you could deploy, which again reduced the space efficiency of SIS. We further optimized transport delivery and completely removed the need for SIS from a transport perspective.  Finally, we made changes to the information store that removed the ability to single instance message bodies (but allowed single instancing of attachments). The result was that SIS no longer provided any real space savings - typically only about 0-20%.
One of our main goals for Exchange 2010 was to provide very large mailboxes at a low cost. Disk capacity is no longer a premium; disk space is very inexpensive and IT shops can take advantage of larger, cheaper disks to reduce their overall cost. In order to leverage those larger capacity disks, you also need to increase mailbox sizes (and remove PSTs and leverage the personal archive and records management capabilities) so that you can ensure that you are designing your storage to be both IO efficient and capacity efficient.
During the development of Exchange 2010, we realized that having a table structure optimized for SIS was holding us back from making the storage innovations that were necessary to achieve our goals. In order to improve the store and ESE, to change our IO profile (from many, small, random IOs to larger, fewer, more sequential IOs), and to resolve our inefficiencies around item count, we had to change the store schema. Specifically, we moved away from a per-database table structure to a per-mailbox table structure:
This architecture, along with other changes to the ESE and store engines (lazy view updates, space hints, page size increase, b+ tree defrag, etc.), netted us not only a 70% reduction in IO over Exchange 2007, but also substantially increased our ability to store more items in critical path folders.
As a result of the new architecture and the other changes to the store and ESE, we had to deal with an unintended side effect.  While these changes greatly improved our IO efficiency, they made our space efficiency worse.  In fact, on average they increased the size of the Exchange database by about 20% over Exchange 2007. To overcome this bloating effect, we implemented a targeted compression mechanism (using either 7-bit or XPRESS, which is the Microsoft implementation of the LZ77 algorithm) that specifically compresses message headers and bodies that are either text or HTML-based (attachments are not compressed as typically they exist in their most compressed state already).  The result of this work is that we see database sizes on par with Exchange 2007.
The below graph shows a comparison of database sizes for Exchange 2007 and Exchange 2010 with different types of message data:
As you can see, Exchange 2007 databases that contained 100% Rich Text Format (RTF) content was our baseline goal when implementing database compression in Exchange 2010. What we found is that with a mix of messaging data (77% HTML, 15% RTF, 8% Text, with an average message size of 50KB) that our compression algorithms are on par with Exchange 2007 database sizes. In other words, we mitigated most of the bloat caused by the lack of SIS.
Is compression the answer to replacing single instancing all together? The answer to that question is that it really does depend. There are certain scenarios where SIS may be viable:
  • Environments that only send Rich-Text Format messages. The compression algorithms in Exchange 2010 do not compress RTF message blobs because they already exist in their most compressible form.
  • Sending large attachments to many users. For example, sending a large (30 MB+) attachment to 20 users.  Even if there were only 5 recipients out of the 20 on the same database, in Exchange 2003 that meant the 30MB attachment was stored once instead of 5 times on that database. In Exchange 2010, that attachment is stored 5 times (150 MB for that database) and isn't compressed. But depending on your storage architecture, the capacity to handle this should be there. Also, your email retention requirements will help here, by forcing the removal of the data after a certain period of time.
  • Business or organizational archives that are used to maintain immutable copies of messaging data benefit from single instancing because the system only has to keep one copy of the data, which is useful when you need to maintain that data indefinitely for compliance purposes.
If you go back through our guidance over the past 10 years, you will never find a single reference to using SIS around capacity planning.  We might mention it has an impact in terms of the database size, but that's it.  All of our guidance has always dictated designing the storage without SIS in mind.  And for those that are thinking about thin provisioning, SIS isn't a reason to do thin provisioning, nor is SIS a means to calculate your space requirements.  Thin provisioning requires an operational maturity that can react quickly to changes in the messaging environment, as well as, a deep understanding of the how the user population behaves and grows over time to sufficiently allocate the right amount of storage upfront.
In summary, Exchange 2010 changes the messaging landscape.  The architectural changes we have implemented enable the commoditization of email - providing very large mailboxes at a low cost.  Disk capacity is no longer a premium.   Disk space is cheap and IT shops can take advantage of larger, cheaper disks to reduce their overall cost.  With Exchange 2010 you can deploy a highly available system with a degree of storage efficiency without SIS at a fraction of the cost that was required with previous versions of Exchange.
So, there you have it. SIS is gone.
 
 
Posted by at No comments:

Outlook Fonts change once you compose a new email or reply to an email

Issue:
 
Everytime once you compose a new email or reply to an email, Your Outlook's new message window shows very big or timy letters.
 
Cause:
 
If your font looks smaller or bigger than the actually configured font size, your zooming factor has been set above or below 100%.
 
Resolutions:
 
You can change it back in the following way:
 
Outlook 2010
When composing click on the Zoom button on the Home tab.
 
Outlook 2007

When composing go to the Format Text tab and click on the Zoom button.
 
 
Previous versions of Outlook
You can only zoom when you have Word set as the email editor. The Zoom function can be found in the View menu.
 
Note:
The change in the zoom factor probably was caused by holding the CTRL button while scrolling. This is an alternative method to change the zoom factor.
 
 
Posted by at No comments:

Wednesday, June 1, 2011

Outlook 2007 support for Exchange 2010 SP1 mailbox Archive

 
Outlook 2007 support for Personal Archives in Exchange 2010 SP1.
 
Exchange 2010 includes Personal Archives, a feature designed to help you reduce the risks from PST files and reduce the costs of discovery. Organizations can provision archive mailboxes for their users, allowing them to store older e-mail that's accessed less frequently in the archive. From the user's perspective, archive mailbox behaves like a PST file, minus the file management overhead and risks of a PST file. For more details, see Understanding Personal Archives in Exchange 2010 documentation. Also check out Exchange GM Perry Clarke's Geek Out With Perry series for a chalk talk video on Exchange Archiving.
In the Exchange 2010 RTM timeframe, users could use Outlook 2010 or Outlook Web App (OWA) to access archive mailboxes. This update extends archive support to Outlook 2007.

How does it work in Outlook 2007?

If an administrator provisions an archive mailbox for a user, it is accessible in Outlook 2007 with the December 2010 Cumulative Update installed. As with Outlook 2010, Outlook 2007 uses the Autodiscover service to obtain information about the user's archive mailbox. This occurs when the user starts Outlook, or at a fixed interval when Outlook is running. The archive mailbox is only accessible when the user is connected to the Exchange server.

Cached Exchange Mode and Archive Mailboxes

In Outlook 2010 and Outlook 2007, users can access archive mailboxes only when they're connected to the Exchange server. The connection can be an RPC (over TCP) connection, or Outlook Anywhere (aka RPC over HTTP). Even if the Outlook profile is configured to use Cached Exchange Mode, the archive mailbox is never cached locally to the user's computer. When the user is no longer connected to Exchange, the archive mailbox becomes inaccessible. The locally cached primary mailbox remains accessible if using Cached Exchange Mode.
Once the archive mailbox is visible in Outlook 2007, users can expand the folder hierarchy, and are able to perform the following operations:
  • Move or copy messages and folders between their primary mailbox and the archive mailbox
  • Move or copy messages and folders between a PST file and their archive mailbox (if access to PST files is not blocked by the administrator).
    Note: In Exchange 2010 SP1, administrators can also use mailbox import requests to import data from PST files to either the user's archive or primary mailbox. For more information, see Understanding Mailbox Import and Export Requests.
  • Export or import messages to and from the archive mailbox
  • Use Inbox Rules to automatically move messages to a folder in the archive mailbox
However, Outlook 2007 does not support the following functionality:
  • Search across primary and archive mailboxes: When a user searches the primary mailbox, and selects All Mailbox Items, Outlook does not search the archive mailbox. Similarly, when the user searches the archive mailbox, the primary mailbox is not searched.
  • Archive policies: In Outlook 2007, users can't use personal tags (also known as archive policies) to move items to the archive mailbox. Any default archive policies for the mailbox continue to be applied. Users can use Outlook Web App to see or apply archive policies.

    Archive policies are retention policy tags with the Move to Archive action. Organizations can use the Default Archive and Retention Policy, or apply custom retention policies to a mailbox. The policies can include a default policy tag (DPT) to move items from the primary mailbox to the archive mailbox, and personal tags which users can apply to messages or folders to move them to archive. For more information, see Understanding Personal Archives, and Understanding Retention Tags and Retention Policies.
With the release of this update, organizations with Office 2007/Outlook 2007 deployed can benefit from Exchange 2010's archiving and retention features.
Posted by at No comments:

Thursday, May 26, 2011

How Offline Address Book Works In Exchange 2007

How Offline Address Book Works In Exchange 2007

A clear understanding of how the offline address book works in exchange helps an admin in troubleshooting the related issues. This article explains how oab works in the 2007 edition.
The Exchange System Attendant service is responsible for the generation of oab. This service is available only on a server that has the mailbox role installed. The SA invokes a dll file called oabgen.dll. To find out the server that is generating the offline address book, launch EMC –> Organizational Configuration –> Mailbox –> OAB tab.
Generation Server OAB
Once you have made too many changes in exchange, you can update the address book by right clicking and selecting Update. By default, oab is updated only once in 24 hours at 5am. You can customize the update schedule depending upon your requirements.
OAB Update
Where exactly are these oab files stored? On a default installtion, the oab files are stored in C:\Program Files\Microsoft\Exchange Server\ExchangeOAB. This folder is shared so that it can be replicated to the CAS server for web distribution.
ExchangeOAB
How does oab end up in public folders? Outlook 2003 and previous versions get oab from the system public folders in exchange. The oab generation server opens the oab folders and updates the file. The oabgen.dll file is responsible for connecting to the public folder.
How does Outlook 2007 get oab files? The server that has the client access role installed (CAS server) is responsible for providing oab files for outlook 2007 clients. For that, CAS server runs a service named Microsoft Exchange File Distribution Service which copies the oab files from the mailbox server (ExchangeOAB folder) to the web distribution point in the CAS server.
File Distribution Service
Where is this web distribution point, one might ask? The web distribution folder is a folder in the file system where the copied oab files are placed. The default location is C:\Program Files\Microsoft\Exchange Server\ClientAccess\OAB.
CAS oab
The web distribution point is updated once in 8 hours. If you want to force an oab update, restart the Exchange File Distribution Service.
Now that you know how oab works and are replicated from the mailbox server to the system folders and web distribution point, you will find it much easier to troubleshoot any issues relating to the offline address book.


Posted by at No comments:

Friday, April 15, 2011

Outlook Doesn't show attachment

Summary: There are some emails from a particular vendor, which contains  attachments. When it arrives in Outlook inbox, there is no paper clip icon, but from the size we can see there is something. If we use OWA to view the message we can see an attachment. If we forward to external web emails like hotmail, yahoo, the attachments are there.
 
In Microsoft word: A MIME-encoded message that includes an inline attachment arrives in Microsoft Exchange Server. You try to access the message from a Microsoft Office Outlook 2003/2007/2010 client. In this scenario, the attachment is hidden, and it is unavailable for download. If you use Microsoft Office Outlook Web Access to view the same message, the inline attachment is still hidden. However, the inline attachment is available for download in Outlook Web Access, and you can click the message and view it.

 

Resolutions:

 

Exchange Server 2010

  1. Stop the Exchange Transport service.
  2. Locate the EdgeTransport.exe.config file. This file is located in the following path: 
    <drive> :\Program Files\Microsoft\Exchange Server\Bin\
  3. In the EdgeTransport.exe.config file, add the following entry between the <appSettings> element and the </appSettings> element:
    <add key="TreatInlineDispositionAsAttachment" value="true" />
  4. Restart the Transport service.

Notes

  • If the TreatInlineDispositionAsAttachment option does not exist or if the option is set to "false," the behavior is the same as the behavior that is mentioned in the "Symptoms" section.
  • If the TreatInlineDispositionAsAttachment option is set to "true," the inline attachment that is not referenced is available for download.

Exchange Server 2007 SP2 or later

  1. Make sure that Exchange Server 2007 Service Pack 2 or later is installed.
  2. Run the following command:
    set-OrganizationConfig -ShowInlineAttachments:$true



Posted by at 1 comment:

Wednesday, April 6, 2011

How to troubleshoot calendar issues in Microsoft Outlook, Microsoft Exchange Server 2007, and Microsoft Exchange Server 2010

Summary:
 
When you need help troubleshooting most calendar issues in Microsoft Outlook and Microsoft Exchange, you have to collect and provide lots of data for the Microsoft support professional. This is primarily because of the complexity of the calendar feature set in Microsoft Office Outlook and Microsoft Exchange Server and because of the varied scenarios and products that affect the calendar data. The troubleshooting data that is needed includes an Exchange Store log for a user. This article describes how to enable Exchange 2007 and Exchange 2010 Store tracing for troubleshooting issues that are related to an Outlook calendar. 

For information about working with Microsoft support to troubleshoot the Outlook calendar in an Exchange environment, visit the following Microsoft website:
http://technet.microsoft.com/en-us/library/cc891495.aspx (http://technet.microsoft.com/en-us/library/cc891495.aspx)
Important This article describes the calendar logging process to use when you work with the support team at Microsoft. It is not intended to provide complete information for you to perform store logging by yourself. There is a risk of performance problems on the Exchange server if logging is not enabled correctly. That is why you should work with the support team during this process.
 
Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 can trace calendar activities that occur in the store. This tracing is performed through the Exchange Troubleshooting Assistant (ExTRA). The tracing can be done per user or per server.

The following steps show how to enable this tracing feature when you work with a Microsoft support engineer on a support case for calendar issues.

Enable Exchange tracing for calendar issues

  1. Identify the user whose mailbox will be traced by this process.

    Note For best performance, you should always identify one user who is encountering the issue, and then trace only that user's mailbox by using per-user tracing.
  2. Start ExTRA. To do this, click Start, click Run, type the following command in the Open box, and then click OK:

    Extra.exe
  3. On the "Welcome to the Exchange Troubleshooting Assistant" page, click Select a task.
  4. On the "Troubleshooting Task Selection Screen" page, click Trace Control.
  5. Click OK when you receive the following warning:

Reference:

 

 
 
Posted by at No comments:

Thursday, March 31, 2011

Exchange Server 2007/2011 Cross Mailbox Search using Export-mailbox

Administrators have always needed a flexible way to search for content simultaneously across multiple mailboxes.  Here are a few scenarios requiring cross-mailbox search, and how the 'export-mailbox' command can be used to get the desired results.
 
Scenario 1: LEGAL DISCOVERY:
 
The administrator needs a way to extract messages from multiple users' mailboxes which contain certain keywords in the subject and/or body for Legal Discovery purposes. In this case, the content found does not need to be deleted, but only extracted to a single target mailbox.
 
Solution:  The administrator will need to use the Export-Mailbox task from the Exchange Management Shell with the –TargetFolder and –TargetMailbox parameters:
 
PS> get-mailbox –Database DB1 | Export-Mailbox –SubjectKeywords "Discovery Keywords" –TargetMailbox Administrator –TargetFolder 'MyData'
 
This will search through all mailboxes on the Mailbox Database DB1 for messages containing the words "Discovery" and "Keywords" in the Subject field and copy these to a folder named MyData in the Administrator's mailbox. A folder will be created for each user mailbox which had matching messages under the "MyData" folder, using the following naming convention: "Recovered Data - <MailboxAlias> - <Timestamp>"
 
Scenario 2: VIRUS THREAT RESPONSE: The administrator needs the ability to rapidly scan a large number of messages across multiple user mailboxes based on specific criteria to identify suspect messages that may be infected by a virus, and perform mass deletion of such email. In this case, the administrator is not required to keep copies of the deleted emails.
 
Solution: The administrator will need to use Export-Mailbox with the –TargetMailbox,-TargetFolder, and –DeleteContent parameters as follows
 
PS> get-mailbox | Export-Mailbox –ContentKeywords "Virus message" –TargetMailbox Administrator –TargetFolder 'MyData' –DeleteContent
 
This will search through all mailboxes in the organization for messages containing the words "Virus message" in the body and copy them to a folder named MyData in the Administrator's mailbox, and delete the original message from the source mailboxes. The administrator can then delete all the messages under "My Data" to ensure that the suspect virus messages are eliminated. In order to delete the items, you will have to use the deletcontent parameter.
 
NOTE: To run the Export-Mailbox cmdlet on a computer that has the Mailbox server role installed, you must log on by using a domain account that has the permissions assigned to the Exchange Server Administrators group on the source server and the target server. The account must also be a member of the local Administrators group on that computer.  You cannot export data from a mailbox in one forest to a mailbox in a different forest. The source and target mailboxes must be in the same forest
For a complete listing of the search criteria that can be used as filters, and other options for the export-mailbox command, please type "Get-help Export-Mailbox" from the Exchange Management Shell. Alternatively, check the Exchange Server 2007/2011 documentation online.
Posted by at No comments:

Monday, March 14, 2011

Re: Outlook 2007 Reminders for archives and additional pst-files

 

I'm storing a couple of my Outlook folders outside of my default mailbox (inside a separate pst-file). When I flag messages in this folder and add a reminder I get the following error;

"The reminder for "<subject>" will not appear because the item is in a folder that doesn't support reminders. Is this OK?"

How can I add reminder support to this folder?

Outlook 2007 and Outlook 2010 do support reminders across folders in additional pst-files but by default this option is disabled.

Description: The reminder for <subject> will not appear because the item is in a folder that doesn't support reminders. Is this OK?
Click on image to enlarge.

To enable reminder support for these pst-files;

  1. Right click on the top of the pst-file and choose Properties.
    Description: Outlook Data File context menu
  2. In the Properties dialog enable the option;
    Display reminders and tasks from this folder in the To-Do Bar
  3. You'll be prompted to restart Outlook. Once restarted, the reminders should work.

If reminders still do not pop-up for you then or when you want to add Reminder support across folders for Outlook 2003 or previous see; Follow Up Flags and reminders

Description: Enable reminders for additional pst-files
Enable reminder support for additional pst-files.

 

Posted by at No comments:

Friday, March 11, 2011

2011 Times Higher Education World Reputation Rankings: Top 50


英国世界大学学术声誉排行榜

 

          

Description: http://i5.hjfile.cn/pic/201103/20110310101252557_859_o.jpg

    英国《泰晤士报高等教育副刊》3月10日发布2011年世界大学学术声誉排行榜，美国哈佛大学位列榜首，中国清华大学和北京大学跻身百强，分列第三十五和第四十三位。
    美国大学在排行榜上独占鳌头，夺得前10名中的7席，并有45所大学进入百强。英国是第二大赢家，剑桥大学和牛津大学名列十强，总共12所英国大学进入百强。日本大学的表现也很抢眼，5所大学跻身百强，其中东京大学名列第八。
    首次发布的世界大学学术声誉排行榜是《泰晤士报高等教育副刊》世界大学排行榜的"子榜"，是根据各大学在教学和科研领域的表现确定的。而一年一度的《泰晤士报高等教育副刊》世界大学排行榜的评定指标多达13个，除教学和科研之外，还包括论文引用情况、科研成果转化收入以及国际化程度等。主编菲尔·巴蒂说，世界大学学术声誉排行榜是在对大学学术表现进行了迄今为止最全面的全球性调查之后排定的。他指出，在国际人才市场对学生、学者和学校管理人员的争夺更为激烈的今天，大学享有良好的学术声誉至关重要。

 

Posted by at No comments:

Wednesday, February 9, 2011

Exchange Auditing log for Mailbox access

One of the new features that service pack 2 of Exchange 2007 server brings is the ability to audit mailbox access at database level.
 
Here is how to enable and view auditing log for mailbox access:
 
 
If you run Exchange 2010 SP1, you can enable auditing log for mailbox access on individual mailbox.
To learn more, please visit Microsoft Technet link below:
 
 
 
Posted by at 1 comment:

Tuesday, February 8, 2011

How to Export LCS user list

This applies to LCS 2005sp1 environments but should also work on OCS2007 environments.

The challenge was to generate a list of LCS enabled users that were not disabled. I have a WMI query that will generate a list of LCS users, but I really wanted to be able to filter out the disabled users.

 

Install Powershell 1.0 or later on LCS server

 

Get-WmiObject msft_sipesusersetting -filter "Enabled = true" | Select-Object DisplayName >LCSuserslist.txt

 

As I had some other needs at the time, I added the telephone information as well to the query. Using get-member you can find a number of other different pieces of useful information to gather as well.

A lot of the 'engine' on how/where to get this information I found here and a nod to Eric Woodford for helping with the only enabled users filter.

 

# NAME: export-activeLCSuser.ps1
#
#
# COMMENT: Requires Quest Active Directory Extension 1.1
#

# Get date for file name
$day = Get-Date -UFormat "%Y%m%d"

Get-QADUser -SizeLimit 0 -LDAPFilter '(&(msRTCSIP-UserEnabled=TRUE)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))' -IncludedProperties 'msRTCSIP-Line' | Select-Object displayName, msRTCSIP-Line, telephoneNumber, Mobile | Export-Csv -Path .\$day-LCSuser.csv
Posted by at 1 comment:
Subscribe to: Posts (Atom)