Exchange 2010 – Converting Legacy Mailboxes to User Mailboxes

How to convert Legacy Mailboxes to regular User Mailboxes after Exchange upgrade

If you recently completed a transition from Exchange 2003/2007 to 2010 you probably noticed that some of the migrated mailboxes are marked as Legacy Mailboxes.

 

 

In order to change all Legacy mailbox to regular mailboxes,  you can run the following PowerShell cmdlet: :

 

Get-Mailbox -ResultSize unlimited -Filter {RecipientTypeDetails -eq “LegacyMailbox”} | Set-Mailbox –ApplyMandatoryProperties

 

In order to convert specific mailboxes to regular mailboxes, run the following PowerShell cmdlet:

Set-Mailbox -Identity -ApplyMandatoryProperties

Posted in Exchange 2010 | Leave a comment

GPO – Deny single user/Group

1. First you need to find the GPO Guid

To Find the group Guide Connect to a dc server and open Active Directory PowerShell

get-gpo -all |select-object DisplayName,id |sort name >c:\gpo.txt

image

 

2. Find in Active directory the GPO with ldap search

That guid is an attribute on an object in Active Directory, so you can query for it:

(&(objectCategory=groupPolicyContainer)(name={D45A4D0F-77BE-4116-9F5B-CF96E81D2DDC}))

image

3.Right Click On the Guid – Properties -security

4.Advanced

5.Add the user/group

6.Deny on – Apply Group Policy

clip_image001

clip_image002

Posted in Active Directory, GPO | Tagged , | Leave a comment

Share Point 2013 – determine the SharePoint version in PowerShell

You can determine which version of SharePoint is installed (2010 = 14, 2013 =15 ) with this line

(Get-PSSnapin Microsoft.SharePoint.PowerShell).Version.Major

You can determine which Build is Installed With this line

(get-spfarm).buildversion

image

To see the build number  friendly names:

SharePoint 2013 Build Numbers

Posted in SharePoint | Tagged , , | Leave a comment

Office 365–Enable First release Option

Set up the release option for your organization

You can change how your organization receives Office 365 updates by following these steps.

Important   It can take up to 24 hours for the below changes to take effect in Office 365. If you opt out of First Release after enabling it, your users may lose access to features that haven’t reached the scheduled release yet.

  1. Sign in to Office 365 with your work or school account.

  2. Go to the Office 365 admin center.

  3. Go to Service settings > Updates.

  4. To disable first release, select Standard under the Standard release heading.

    To enable first release choose Entire organization or Select people and follow the steps below.

    Standard and first release programs

    Note    If you don’t see this option in your admin center, your subscription will soon be updated with it and you can change the setting then.

Select people for First Release

Follow these steps to select individual people for First Release. You might, for example, add your IT staff for First Release so they can review features before the rest of your organization. Enable First Release with select people following these steps.

  1. Go to the Office 365 admin center.

  2. Go to Service settings > Updates.

  3. Under first release, choose Select people.

    Note    If you don’t see this option in your admin center, your subscription will soon be updated with it and you can change the setting then.

  4. Choose Pick people to add users individually and then use the people picker to select them for first release.

    Office 365 release programs add users

    Or,

  5. Choose Bulk add to add a larger group using a file that contains each person’s email address.

    Bulk add users in Office 365 First Release

    This is similar to how you bulk add users in the admin center.

    Bulk add users to Office 365 release programs

Note   First Release Select People currently only applies to Office 365 top navigation and Exchange Online.

 

Source: https://support.office.com/en-us/article/Office-365-release-options-3b3adfa4-1777-4ff0-b606-fb8732101f47

Posted in Office365 | Tagged , | Leave a comment

Move Mailbox failed – Mailbox size exceeds target quota

Open ADSIEDIT.MSC

 

Find the user and change the value  ‘mBDUseDefaults’  to True wait a few minutes and try again.

 

Good Luck סמיילי

Posted in Exchange 2003, Exchange 2010, Exchange 2013, Microsoft Exchange, Migration | Leave a comment

Error : 1058 Group Policy

The processing of Group Policy failed. Windows attempted to read the file \\domain.local\sysvol\ac.idc\Policies\{2EDE7444-0440-4F4E-BDF7-AD38380F3897}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:

a) Name Resolution/Network Connectivity to the current domain controller.

b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).

c) The Distributed File System (DFS) client has been disabled

clip_image001

In My case, the User Policy can’t apply because the user account has too many groups, which cause a too large Kerberos token size.

Solution :

You can resolve this issue by installing the hotfix and then:

1. Start Registry Editor (Regedt32.exe).

2. Locate and click the following key in the registry:
System\CurrentControlSet\Control\Lsa\Kerberos\Parameters

3. If this key is not present, create the key. To do so:

4. Click the following key in the registry:
System\CurrentControlSet\Control\Lsa\Kerberos

5. On the Edit menu, click Add Key.

6. Create a Parameters key.

7 .Click the new Parameters key.

8. On the Edit menu, click Add Value, and then add the following registry value:
Value name: MaxTokenSize
Data type: REG_DWORD
Radix: Decimal
Value data: 65535

clip_image001[4]

Or You can just remove some groups where the user belong in the old / new domain

Good luck 🙂

Posted in GPO | Leave a comment

Invoke-Command in PowerShell script without password