SolutionCorner

Virtual Machine Movement: Sometime we migrate the VM from one physical host to another physical host by exporting and importing.However,sometimes we face "access denied" problem while try to start VM. Please run the below powershell COMMAND: icacls "E:\Hyper-V\Virtual Hard Disks\Harddisk.vhdx" /grant "NT VIRTUAL MACHINE\B4E6983D-1A09-4DE2-B7A6-DD00132EE065":(F) For details : https://charbelnemnom.com/2014/08/an-attempt-to-initialize-vm-saved-state-failed-could-not-create-or-access-saved-state-file-hyperv-scvmm/

Sometime you had this same problem using Server 2012 Std  or Server 2012 R2 . Iyou tried various options of taking ownership of the parent folder because the Security properties of the folder. you tried  trying to delete were blank, using CMD and Dir /x etc. you even tried sharing the parent folder and then delete it. None of them worked. When you tried Dir /x Server 2012 or 2012 R2 doesn't show the 8 character filename with the ~1. you tried typing it in yourself, but that didn't work either. you then found that there was a space at the end of the folder name. you then tried all the CMD options again using a space, still no luck. This solution should help  you out: Open CMD and then type: rd /s "\\?\D:\bad\folder\path " example: rd /s "\\?\D:\Sharedata\folder1\folder2 " - note the space after folder2 as per the space in the folder name. Obviously D: is the drive that has the folder on it. This worked for me

Get-ADUser -Filter * -Properties sn, DisplayName, mail, Title, Mobile| where {$_.enabled -eq "True"} |select sn, DisplayName, mail, Title, Mobile | Export-CSV "C\Mobile_Information.csv"

Power Shell Script for creating bulk users from CSV in Active Directory.All the Column name should be available such as SamAccountName,DisplayName,GivenName,Surname and more. ᐅ Import-Csv .\Users.csv | foreach-object { $userprinicpalname = $_.SamAccountName + "@ contoso.com "; New-ADOrganizationalUnit -Name Hardware -Path "ou=IT,dc=dc1,dc=com";New-ADUser -SamAccountName $_.SamAccountName -UserPrincipalName $userprinicpalname -Name $_.name -DisplayName $_.name -GivenName $_.cn -SurName $_.sn -Department $_.Department -Path $_.path; Set-ADAccountPassword -identity $_.SamAccountName -NewPassword (ConvertTo-SecureString -AsPlainText $_.Password -Force) -Reset ; Enable-ADAccount -identity $_.SamAccountName; Set-ADUser -Identity $_.SamAccountName -ChangePasswordAtLogon $true}

If you have more than one DC please run the following script in each DC for getting user logon information. ᐅGet-ADUser -Filter * -Properties * | Select Displayname,sn,@{N='LastLogon'; E={[DateTime]::FromFileTime($_.LastLogon)}} | Export-csv c:\userlastlogoninfo.csv

Please run  the following shell script as administrator in AD Power Shell command line  for individual user . ᐖ Get-ADPrincipalGroupMembership username | Select name | Export-Csv c:\group.csv

Please follow the below link for your information: ➤Exchange Server Email Delivery Troubleshooting Link

If the disabled archive still exists in the database, you can reconnect it to the primary mailbox.   Solution: You can get the archive quid by searching the database with the following: Get-MailboxStatistics -Database Archive | Export-Csv c:\archivestat.csv Enable-mailbox -identity <alias of user> -ArchiveGUID <archiveMailboxGuid> -ArchiveDatabase <archiveDB> -Archive

In practical, there are several ways to monitor the mailbox moves: Using the Exchange Management Shell (EMC) Using the Exchange Management Console (EMS) Using the performance monitor We’ll go through all of the above procedures and define whichever method you prefer as effectively as possible. ➤Exchange Management Shell: There are number of options available.when using the EMS, actually have several cmdlet options to monitor the move requests: Get-MoveRequest Get-MoveRequestStatistics Get-MailboxStatistics ➤Get-MoveRequest: Get-MoveRequest ; by itself, this PowerShell cmdlet will only give you a brief overview of the move requests which are currently active or queued. Without using the | fl command in the pipeline, it will only display: displayname status targetdatabase Which may , in some cases, be enough, particularly if you only want an overview of the move-requests currently active or queued, and you’re not interested in more detailed information...

Solution: Set-CASMailbox -Identity: "EmailAlias" -ActiveSyncBlockedDeviceIDs: "<DeviceID_1>","<DeviceID_2>"

Solution:   Get-Mailbox -ResultSize unlimited -Filter {RetentionPolicy -ne $null} | Set-Mailbox -RetentionPolicy $null

Scenario: When trying to log into a 2012, 2012 R2 server, you receive the following error: Error: This info is displayed in the application log (Event 1509). “Windows cannot copy file \\?\C:\Users\Default\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm to location \\?\C:\Users\<username>\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm. This error may be caused by network problems or insufficient security rights.” Solution:  There are two Solution which will be fixer for the above problem. 1. Go to the permissions of the source file and make sure you select the permissions to be inherited from advanced security settings: File Path: C:\Users\<username>\AppData\Local\Microsoft\Exchange Server\v15\Configuration14720_100.sqm. 2. Delete the file.

Here's weird one. While a mailbox is moved from Exchange 2013 to Exchange 2016 or in local for a mailbox with an in-place archive. A new migration batch is created for the user and it completes in short order, but the mailbox and archive are not moved. The number of Total, Synced, Failed, and Successful mailboxes for the batch is zero. You get a notification email saying the batch completed success fully, but no mailboxes were moved or synced. When you look at the details of the migration batch in EMS you see that the Validation Warning Count is 1 and the Validation Warnings show, "Error:The user already exists, but the migration batch that includes it couldn't be found. Before you try migrating the user within a batch again, please remove the existing user by running the Remove-MigrationUser cmdlet." A "MigrationUser" object is created for each user who is in the process of being migrated or the migration has not been completed, so it remains...