I ran into this error While installing Dirsync on a DC server
The error shown “The Server is not operational”
Event log: “Enable-MSOnlinePasswordSync failed. Error: The pipeline has been stopped.”
The solution was simply to log off and log on to the DC server.
Good luck !
This guide provide the steps to take in order to create new Database in Exchange using Netapp storage and snap drive
In this case , I’m using Netapp 2020
1. Check Space Availability
Available storage in NetApp filers is contained in aggregates.
– In NetApp onCommand System Manager select the aggregate section and check for available space:
2.Create Volume
Now that you are sure that you have Enough disk space available you can create a new volume
-In NetApp onCommand System Manager select the Volume section and then click on "Create"
You’re now presented with the "Create Volume window"
Name: provide the name for the volume
Aggregate: choose the aggregate
Storage Type: SAN
Total size: type the size of the DB
check the "Thin provisioned" check box if you want.
Navigate to Storage Efficiency
Check the "Enable storage Efficiency" check box - this will let you control data growth to increase storage utilization, regain capacity, and improve IT performance
*Do the same for the log DB
3. Create Qtree
In NetApp onCommand System Manager select the Qtrees section and then click on "Create"
You’re now presented with the "Create Qtree window"
Name: provide the name for the Qtree
Volume: Select the volume you created in step 2
oplocks: By default its enabled – I usually keep it that way –This options means that A client can work with a file (read or write it) without regularly reminding the server that it needs access to that file, which improves performance by reducing network traffic.
Check Inherit Volume security style
Click Create.
*Do the same for the log DB
4. Create LUN with snap Drive
Connect to Exchange server and open Snap Drive
Navigate to "Disks" and click on Create disk
This will start the “Create disk Wizard”, and you can click ‘Next’ on the welcome page
Select the new Volume-Qtree you created
provide the name for the New Lun
Click Next
Select – Dedicated
Assign a Drive letter and the LUN size
Click next
Select the initiator , in my case its VMware ESXI
select Manual
Select the initiator group
Select Store with virtual machine
Finish the wizard
*Do the same for the Log DB
5. Format the new Drive
On the Exchange server Navigate to – "My computer"
Right click on the new Drive and click on Format
Under Allocation Unit size choose – 64 kilobytes
Check – Quick format
Start
*Do the same for the log DB
The next step is to create the DB in exchange.
Good luck !
In order to import an Microsoft volume license to Office365 tenant , take the following steps :
1. Go to – http://office.microsoft.com/setup365
2. under "Already an Office 365 customer?" click "Sign in"
Enter your Office 365 account
Enter your product key (from your account on Microsoft Volume Licensing Service Center)
Good Luck!
This could be caused by a number of problems such as:
The information below may help to resolve the problem:
Computer DNS name is "dc2.domain"
Replica set member name is "DC2"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is
FRS error status code is FrsErrorMismatchedJournalId
Steps to take:
1. Stop the File Replication service on the domain controller DC1
2. Start Registry Editor
3. Locate and then click the BurFlags value under the following key in
the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
4. On the Edit menu, click DWORD, click Hex, type D2, and then click
OK.
5. Quit Registry Editor.
6. Restart the File Replication Service
4. Backup:
get-vmhost "Host.Domain.local"| get-vmhostfirmware -BackupConfiguration -DestinationPath “C:\BackupHost”
*BackupHost is a directory that I created, you can put any path where you want the backups to be stored.
5.Restore:
Get-vmhost “Host.Domain.local” | Set-VMHostFirmware -Restore -DestinationPath C:download
Or whereever you stored the backup config.
One of my customer got this error after adding a new SMTP domain to mailboxes.
In his case he add the email address directly from the AD to some mailboxes and then got this error when trying to send them an email to the new address.
The solution for his problem was to create a new recipient policy and add to it the new external domain.
Create a new Recipient policy:
GO to Exchange system manager –> first organization –> recipients –> Recipients policies
you can add the domain to the default policy if you need to add it to all mailboxes or you can set a new policy for specific mailboxes.
In this case I created a policy for specific mailbox filtered by OU
1. right click on Recipient policy –> New recipient policy
2. Choose – Email address
\
3. Modify –>find –> Organization units
4. Select the OU
5. New SMTP Address
6. Write @Yourdomain
Good luck!
“Changes to the distribution list membership cannot be saved. You do not have sufficient permission to perform this operation on this object.”
In Exchange 2010 you need to enable the ability to manage distribution groups
Logon to ECP –> under Roles & Auditing –>”Default Role Assignment Policy”
Under Distribution Group—> check “MyDistributionGroup”
This option will allow users to add/remove members to distribution groups they own.
When you try to add a sub domain to office365 via the Office365 portal , you get this error:
Can’t add domain
“Sub.Mydomain.com is a subdomain of a domain which was added by using the Microsoft Online Services Module for Windows PowerShell.
You must also use this tool to add Sub.Mydomain.com to Microsoft Online Services.”
Two thing you need to do in order to add a subdomain
1. add the domain using the Windows Azure Active Directory PowerShell
2. Do it on your ADFS server or you will get this message :
“Failed to connect to Active Directory Federation Services 2.0 on the local machine”
Add a sub domain using Azure Active Directory PowerShell:
Once the command will issued you receive this message “Successfully added ” Your sub domain”
Good luck 
Prerequisites
Install Dirsync :
1. Run the Dirsync.exe application you downloaded
Click Next
2. Accept the License Terms
3. choose your installation path
4. It takes 10 minute or longer to complete
5. Click Next
6. choose to run the configuration wizard
Configure Dirsync to work with you Office365 Tenant
1. Click Next
2. Type your Office365 tenant administrator
3. Type an enterprise admins user from your local AD
4. if your deployment is in an hybrid environment click – Enable Hybrid Deployment
5. Enable Password Sync
You can check the synchronization status with the miisclient.exe tool :
C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\Miisclient.exe
You can monitor the progress of Password Sync through the event log of the machine that is running the Directory Sync tool.
Determining the Password Sync status
You can determine which users have successfully had their passwords synchronized by reviewing the events that match the following criteria:
Source : Directory Synchronization
Event ID :656 , 657
The events with the Event ID 656 provide a report of processed password change requests:
The corresponding events with the ID 657 provide the result for these requests:
![clip_image001[4]](https://www.itblog.co.il/wp-content/uploads/2013/07/clip_image0014.jpg)
In the events, the affected objects are identified by their anchor and the DN value. The anchor value corresponds to the ImmutableId value that is returned for a user by the Get-MsoUser cmdlet.
In addition to the object identifiers, Event ID 656 provides the date the user’s password was changed in the on-premises Active Directory::
Event ID 657 has a Result field in addition to the source object identifiers to indicate the status of synchronization for that user object.
A successfully synchronized password is in an event with the Event ID 657 indicated by a value of Success for the Result attribute. When a password synchronization attempt failed, the value of the Result attribute is Failure:
Disabling Password Sync
You disable Password Sync by re-running the Directory Sync tool Configuration Wizard.
When prompted by the Wizard, de-select the “Enable Password Synchronization” checkbox.
Note
This process will trigger a full synchronization. Full synchronization cycles generally take longer than other sync cycles to complete.
After running the Configuration Wizard, your tenant will no longer be synchronizing passwords.
New password changes will not synchronize to the cloud.
Users that previously had their passwords synchronized will be able to continue logging in with those passwords until they manually change their passwords in the cloud.
Good luck 
[AMSPRD0510CA019] Post-move cleanup failed. The operation will try again in 30 seconds (5/6).
[AMSPRD0510CA019] Target mailbox ‘User name’ was updated on domain controller ‘AMSPRD0510DC006.eurprd05.prod.outlook.com’.
[AMSPRD0510CA019] Unable to update Active Directory information for the source mailbox at the end of the move. Error: UpdateMovedMailboxPermanentException.
[AMSPRD0510CA019] Waiting for mailbox changes to replicate.
[AMSPRD0510CA019] Request is complete.
I got this warning when I moved an Exchange 2003 mailbox to the cloud.
In the last step of the move, the Onpremise mailbox should be converted into a mail user.
Attributes and target address should be pointing to the cloud.
In this case, it seems like, the on-premise mailbox was not getting converted into a remote mailbox and the attributes need to change manually.
Before changing anything, check that you still see the old mailbox, if so backup all the x500 address.
From Adsiedit – properties on the AD User:
First clear the following attributes
1. homemdb
2. homemta
3. msExchHomeServerName
4. msExchPoliciesExcluded
Now add the following:
1. msExchRemoteRecipientType="4"
2. msExchRecipientDisplayType="-2147483642
3. msExchRecipientTypeDetails="2147483648"
4. targetaddress: SMTP:alias@tenant.mail.onmicrosoft.com
Add x500 address you backed up if they don’t exists
Now Sync AD using Dirsync
That’s worked for me.
Good luck J
Get every new post delivered to your Inbox
Join other followers
