Cannot change default OU for new Distribution Groups in Exchange 2010 The 2019 Stack Overflow Developer Survey Results Are InEnforce the use of distribution groups in Exchange 2010Exchange 2010 Cmdlets for Sent Items in a Distribution groupExchange 2010 disable authentication to distribution groups by defaultDoes Microsoft Exchange 2010 have two kinds of Distribution Groups?Exchange Powershell - Creating Distribution GroupsPowershell execution policy within SQL ServerExchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works LocallyExchange Dropping Messages to Distribution GroupAdding AD groups using powershellCannot log into Exchange Management Console, Kerberos auth failed, cannot determine content type of HTTP response from destination computer

What could be the right powersource for 15 seconds lifespan disposable giant chainsaw?

Why is it "Tumoren" and not "Tumore"?

Why do some words that are not inflected have an umlaut?

Are there any other methods to apply to solving simultaneous equations?

Can the Protection from Evil and Good spell be used on the caster?

Should I use my personal or workplace e-mail when registering to external websites for work purpose?

Access elements in std::string where positon of string is greater than its size

Why do UK politicians seemingly ignore opinion polls on Brexit?

Is three citations per paragraph excessive for undergraduate research paper?

How to make payment on the internet without leaving a money trail?

What spell level should this homebrew After-Image spell be?

What do the Banks children have against barley water?

Is bread bad for ducks?

What does "sndry explns" mean in one of the Hitchhiker's guide books?

What is the motivation for a law requiring 2 parties to consent for recording a conversation

Could a US political party gain complete control over the government by removing checks & balances?

Is this food a bread or a loaf?

Patience, young "Padovan"

Manuscript was "unsubmitted" because the manuscript was deposited in Arxiv Preprints

How to reverse every other sublist of a list?

Does duplicating a spell with Wish count as casting that spell?

Inline version of a function returns different value than non-inline version

What tool would a Roman-age civilization have to grind silver and other metals into dust?

Extreme, unacceptable situation and I can't attend work tomorrow morning



Cannot change default OU for new Distribution Groups in Exchange 2010



The 2019 Stack Overflow Developer Survey Results Are InEnforce the use of distribution groups in Exchange 2010Exchange 2010 Cmdlets for Sent Items in a Distribution groupExchange 2010 disable authentication to distribution groups by defaultDoes Microsoft Exchange 2010 have two kinds of Distribution Groups?Exchange Powershell - Creating Distribution GroupsPowershell execution policy within SQL ServerExchange 2010 PowerShell: Value.ToMB() Method Fails Remotely but Works LocallyExchange Dropping Messages to Distribution GroupAdding AD groups using powershellCannot log into Exchange Management Console, Kerberos auth failed, cannot determine content type of HTTP response from destination computer



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








1















I'm trying to use the following command to set the default OU for new distribution groups in Exchange 2010:



Set-OrganizationConfig -DistributioNGroupDefaultOU 'corp.company.com/Employees/MailingList' but I am getting the error:



> Cannot process argument transformation on parameter
> 'CustomerFeedbackEnabled'. Cannot convert value "System.String" to
> type "System.Nullable`1[System.Boolean]", parameters of this type only
> accept booleans or numbers, use $true, $false, 1 or 0 instead.
> + CategoryInfo : InvalidData: (:) [Set-OrganizationConfig], ParameterBindin...mationException
> + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-OrganizationConfig


I saw an online tutorial that suggested this method but it doesn't seem to be working for me. I've tried setting the CustomerFeedbackEnabled param but it just keeps asking for more and more params.



I've also tried specifying the OU in the LDAP 'OU=MailingList,OU=Employees,DC=CORP,DC=COMPANY,DC=COM' format to no avail.



Any suggestions?










share|improve this question






























    1















    I'm trying to use the following command to set the default OU for new distribution groups in Exchange 2010:



    Set-OrganizationConfig -DistributioNGroupDefaultOU 'corp.company.com/Employees/MailingList' but I am getting the error:



    > Cannot process argument transformation on parameter
    > 'CustomerFeedbackEnabled'. Cannot convert value "System.String" to
    > type "System.Nullable`1[System.Boolean]", parameters of this type only
    > accept booleans or numbers, use $true, $false, 1 or 0 instead.
    > + CategoryInfo : InvalidData: (:) [Set-OrganizationConfig], ParameterBindin...mationException
    > + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-OrganizationConfig


    I saw an online tutorial that suggested this method but it doesn't seem to be working for me. I've tried setting the CustomerFeedbackEnabled param but it just keeps asking for more and more params.



    I've also tried specifying the OU in the LDAP 'OU=MailingList,OU=Employees,DC=CORP,DC=COMPANY,DC=COM' format to no avail.



    Any suggestions?










    share|improve this question


























      1












      1








      1








      I'm trying to use the following command to set the default OU for new distribution groups in Exchange 2010:



      Set-OrganizationConfig -DistributioNGroupDefaultOU 'corp.company.com/Employees/MailingList' but I am getting the error:



      > Cannot process argument transformation on parameter
      > 'CustomerFeedbackEnabled'. Cannot convert value "System.String" to
      > type "System.Nullable`1[System.Boolean]", parameters of this type only
      > accept booleans or numbers, use $true, $false, 1 or 0 instead.
      > + CategoryInfo : InvalidData: (:) [Set-OrganizationConfig], ParameterBindin...mationException
      > + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-OrganizationConfig


      I saw an online tutorial that suggested this method but it doesn't seem to be working for me. I've tried setting the CustomerFeedbackEnabled param but it just keeps asking for more and more params.



      I've also tried specifying the OU in the LDAP 'OU=MailingList,OU=Employees,DC=CORP,DC=COMPANY,DC=COM' format to no avail.



      Any suggestions?










      share|improve this question
















      I'm trying to use the following command to set the default OU for new distribution groups in Exchange 2010:



      Set-OrganizationConfig -DistributioNGroupDefaultOU 'corp.company.com/Employees/MailingList' but I am getting the error:



      > Cannot process argument transformation on parameter
      > 'CustomerFeedbackEnabled'. Cannot convert value "System.String" to
      > type "System.Nullable`1[System.Boolean]", parameters of this type only
      > accept booleans or numbers, use $true, $false, 1 or 0 instead.
      > + CategoryInfo : InvalidData: (:) [Set-OrganizationConfig], ParameterBindin...mationException
      > + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-OrganizationConfig


      I saw an online tutorial that suggested this method but it doesn't seem to be working for me. I've tried setting the CustomerFeedbackEnabled param but it just keeps asking for more and more params.



      I've also tried specifying the OU in the LDAP 'OU=MailingList,OU=Employees,DC=CORP,DC=COMPANY,DC=COM' format to no avail.



      Any suggestions?







      exchange exchange-2010 powershell organizational-unit






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 5 '12 at 0:22







      tacos_tacos_tacos

















      asked Jan 4 '12 at 21:08









      tacos_tacos_tacostacos_tacos_tacos

      1,57194783




      1,57194783




















          2 Answers
          2






          active

          oldest

          votes


















          0














          You are trying to do exactly what the article specifies won't work!



          You need to pass on the Distinguished Name of the OU for this to work, like this:



          Set-OrganizationConfig -DistributionGroupDefaultOU "OU=MailingList,OU=Employees,DC=corp,DC=company,DC=com"


          Update: apparently you are not the first to have this issue with parameters passed to the Set-OrganizationConfig cmdlet. If you are using Exchange 2010 RTM, please try and install Exchange 2010 SP1






          share|improve this answer

























          • Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

            – tacos_tacos_tacos
            Jan 5 '12 at 0:22












          • I'll install SP1 tonight and see if that helps - it needs to be done anyway

            – tacos_tacos_tacos
            Jan 5 '12 at 16:41


















          0














          I kept getting the same error message even though my OU designation was 100% correct. I was finally able to set this config in my Exchange 2010.



          Turns out my problem wasn't the formatting of my OU information as all the posts suggested. I have a multi-domain forest. My users (as is the OU I wanted to use for my DistributionGroupDefaultOU) are all in a child domain of the root domain. All my email addresses use the root domain structure. I had the OU information 100% correct using either the OU=, DC=...etc. format or the domain/OU format but still got the error. Frustrating!!! Finally I thought to add the "DomainController" switch to the command pointing to a DC in the child domain and the command was processed successfully! On reflection, the earlier error message had been correct,,, the OU could not be found in the domain (or on the DC) the command (or rather Exchange) was using at the time. When I pointed the command to the correct DC (in the correct domain) the command worked.




          As example, here's what I have:



          • root domain= example.com (DC=Example,DC=com)

          • child domain= staff.example.com ("DC=STAFF,DC=Example,DC=com)

          • all my user accounts are in staff.example.com

          • all email addresses= username@example.com


          • my desired "DistributionGroupDefaultOU"= Groups (in root of staff.example.com)



            (OU=Groups,DC=STAFF,DC=Example,DC=com)


          Below is what finally worked for me:



          Set-OrganizationConfig -DomainController "DC1.staff.example.com" -DistributionGroupDefaultOU "OU=Groups,DC=STAFF,DC=Example,DC=com"


          Possibly my solution might also work for others having the same problem if they have a single domain forest. I suspect my problem was caused by my Exchange 2010 server talking to a DC in a different domain in the forest than the one which contained the OU I was aiming for. Hope this helps someone else out.



          BTW - to get the OU format 100% correct for your command, use "Active Directory Users + Computers". On the menu bar: under "view" make sure "Advanced Features" is check marked. Then find the OU you want to use for your default location, on that OU right click and select properties. Go to the "Attribute Editor" tab. scroll down to "distinguishedName" and double click it. Copy the "Value" to your clip board. Use that for your OU switch in the PowerShell command.






          share|improve this answer

























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "2"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f346699%2fcannot-change-default-ou-for-new-distribution-groups-in-exchange-2010%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            You are trying to do exactly what the article specifies won't work!



            You need to pass on the Distinguished Name of the OU for this to work, like this:



            Set-OrganizationConfig -DistributionGroupDefaultOU "OU=MailingList,OU=Employees,DC=corp,DC=company,DC=com"


            Update: apparently you are not the first to have this issue with parameters passed to the Set-OrganizationConfig cmdlet. If you are using Exchange 2010 RTM, please try and install Exchange 2010 SP1






            share|improve this answer

























            • Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

              – tacos_tacos_tacos
              Jan 5 '12 at 0:22












            • I'll install SP1 tonight and see if that helps - it needs to be done anyway

              – tacos_tacos_tacos
              Jan 5 '12 at 16:41















            0














            You are trying to do exactly what the article specifies won't work!



            You need to pass on the Distinguished Name of the OU for this to work, like this:



            Set-OrganizationConfig -DistributionGroupDefaultOU "OU=MailingList,OU=Employees,DC=corp,DC=company,DC=com"


            Update: apparently you are not the first to have this issue with parameters passed to the Set-OrganizationConfig cmdlet. If you are using Exchange 2010 RTM, please try and install Exchange 2010 SP1






            share|improve this answer

























            • Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

              – tacos_tacos_tacos
              Jan 5 '12 at 0:22












            • I'll install SP1 tonight and see if that helps - it needs to be done anyway

              – tacos_tacos_tacos
              Jan 5 '12 at 16:41













            0












            0








            0







            You are trying to do exactly what the article specifies won't work!



            You need to pass on the Distinguished Name of the OU for this to work, like this:



            Set-OrganizationConfig -DistributionGroupDefaultOU "OU=MailingList,OU=Employees,DC=corp,DC=company,DC=com"


            Update: apparently you are not the first to have this issue with parameters passed to the Set-OrganizationConfig cmdlet. If you are using Exchange 2010 RTM, please try and install Exchange 2010 SP1






            share|improve this answer















            You are trying to do exactly what the article specifies won't work!



            You need to pass on the Distinguished Name of the OU for this to work, like this:



            Set-OrganizationConfig -DistributionGroupDefaultOU "OU=MailingList,OU=Employees,DC=corp,DC=company,DC=com"


            Update: apparently you are not the first to have this issue with parameters passed to the Set-OrganizationConfig cmdlet. If you are using Exchange 2010 RTM, please try and install Exchange 2010 SP1







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Jan 5 '12 at 1:04

























            answered Jan 4 '12 at 23:56









            Mathias R. JessenMathias R. Jessen

            22.7k35089




            22.7k35089












            • Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

              – tacos_tacos_tacos
              Jan 5 '12 at 0:22












            • I'll install SP1 tonight and see if that helps - it needs to be done anyway

              – tacos_tacos_tacos
              Jan 5 '12 at 16:41

















            • Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

              – tacos_tacos_tacos
              Jan 5 '12 at 0:22












            • I'll install SP1 tonight and see if that helps - it needs to be done anyway

              – tacos_tacos_tacos
              Jan 5 '12 at 16:41
















            Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

            – tacos_tacos_tacos
            Jan 5 '12 at 0:22






            Hi Judas, I should have mentioned, I had tried this as well; in fact that format was my first attempt. If you check out the article it also shows a totally different error thrown when you attempt to do it in the form with the back slashes. So I do not think this applies here.

            – tacos_tacos_tacos
            Jan 5 '12 at 0:22














            I'll install SP1 tonight and see if that helps - it needs to be done anyway

            – tacos_tacos_tacos
            Jan 5 '12 at 16:41





            I'll install SP1 tonight and see if that helps - it needs to be done anyway

            – tacos_tacos_tacos
            Jan 5 '12 at 16:41













            0














            I kept getting the same error message even though my OU designation was 100% correct. I was finally able to set this config in my Exchange 2010.



            Turns out my problem wasn't the formatting of my OU information as all the posts suggested. I have a multi-domain forest. My users (as is the OU I wanted to use for my DistributionGroupDefaultOU) are all in a child domain of the root domain. All my email addresses use the root domain structure. I had the OU information 100% correct using either the OU=, DC=...etc. format or the domain/OU format but still got the error. Frustrating!!! Finally I thought to add the "DomainController" switch to the command pointing to a DC in the child domain and the command was processed successfully! On reflection, the earlier error message had been correct,,, the OU could not be found in the domain (or on the DC) the command (or rather Exchange) was using at the time. When I pointed the command to the correct DC (in the correct domain) the command worked.




            As example, here's what I have:



            • root domain= example.com (DC=Example,DC=com)

            • child domain= staff.example.com ("DC=STAFF,DC=Example,DC=com)

            • all my user accounts are in staff.example.com

            • all email addresses= username@example.com


            • my desired "DistributionGroupDefaultOU"= Groups (in root of staff.example.com)



              (OU=Groups,DC=STAFF,DC=Example,DC=com)


            Below is what finally worked for me:



            Set-OrganizationConfig -DomainController "DC1.staff.example.com" -DistributionGroupDefaultOU "OU=Groups,DC=STAFF,DC=Example,DC=com"


            Possibly my solution might also work for others having the same problem if they have a single domain forest. I suspect my problem was caused by my Exchange 2010 server talking to a DC in a different domain in the forest than the one which contained the OU I was aiming for. Hope this helps someone else out.



            BTW - to get the OU format 100% correct for your command, use "Active Directory Users + Computers". On the menu bar: under "view" make sure "Advanced Features" is check marked. Then find the OU you want to use for your default location, on that OU right click and select properties. Go to the "Attribute Editor" tab. scroll down to "distinguishedName" and double click it. Copy the "Value" to your clip board. Use that for your OU switch in the PowerShell command.






            share|improve this answer





























              0














              I kept getting the same error message even though my OU designation was 100% correct. I was finally able to set this config in my Exchange 2010.



              Turns out my problem wasn't the formatting of my OU information as all the posts suggested. I have a multi-domain forest. My users (as is the OU I wanted to use for my DistributionGroupDefaultOU) are all in a child domain of the root domain. All my email addresses use the root domain structure. I had the OU information 100% correct using either the OU=, DC=...etc. format or the domain/OU format but still got the error. Frustrating!!! Finally I thought to add the "DomainController" switch to the command pointing to a DC in the child domain and the command was processed successfully! On reflection, the earlier error message had been correct,,, the OU could not be found in the domain (or on the DC) the command (or rather Exchange) was using at the time. When I pointed the command to the correct DC (in the correct domain) the command worked.




              As example, here's what I have:



              • root domain= example.com (DC=Example,DC=com)

              • child domain= staff.example.com ("DC=STAFF,DC=Example,DC=com)

              • all my user accounts are in staff.example.com

              • all email addresses= username@example.com


              • my desired "DistributionGroupDefaultOU"= Groups (in root of staff.example.com)



                (OU=Groups,DC=STAFF,DC=Example,DC=com)


              Below is what finally worked for me:



              Set-OrganizationConfig -DomainController "DC1.staff.example.com" -DistributionGroupDefaultOU "OU=Groups,DC=STAFF,DC=Example,DC=com"


              Possibly my solution might also work for others having the same problem if they have a single domain forest. I suspect my problem was caused by my Exchange 2010 server talking to a DC in a different domain in the forest than the one which contained the OU I was aiming for. Hope this helps someone else out.



              BTW - to get the OU format 100% correct for your command, use "Active Directory Users + Computers". On the menu bar: under "view" make sure "Advanced Features" is check marked. Then find the OU you want to use for your default location, on that OU right click and select properties. Go to the "Attribute Editor" tab. scroll down to "distinguishedName" and double click it. Copy the "Value" to your clip board. Use that for your OU switch in the PowerShell command.






              share|improve this answer



























                0












                0








                0







                I kept getting the same error message even though my OU designation was 100% correct. I was finally able to set this config in my Exchange 2010.



                Turns out my problem wasn't the formatting of my OU information as all the posts suggested. I have a multi-domain forest. My users (as is the OU I wanted to use for my DistributionGroupDefaultOU) are all in a child domain of the root domain. All my email addresses use the root domain structure. I had the OU information 100% correct using either the OU=, DC=...etc. format or the domain/OU format but still got the error. Frustrating!!! Finally I thought to add the "DomainController" switch to the command pointing to a DC in the child domain and the command was processed successfully! On reflection, the earlier error message had been correct,,, the OU could not be found in the domain (or on the DC) the command (or rather Exchange) was using at the time. When I pointed the command to the correct DC (in the correct domain) the command worked.




                As example, here's what I have:



                • root domain= example.com (DC=Example,DC=com)

                • child domain= staff.example.com ("DC=STAFF,DC=Example,DC=com)

                • all my user accounts are in staff.example.com

                • all email addresses= username@example.com


                • my desired "DistributionGroupDefaultOU"= Groups (in root of staff.example.com)



                  (OU=Groups,DC=STAFF,DC=Example,DC=com)


                Below is what finally worked for me:



                Set-OrganizationConfig -DomainController "DC1.staff.example.com" -DistributionGroupDefaultOU "OU=Groups,DC=STAFF,DC=Example,DC=com"


                Possibly my solution might also work for others having the same problem if they have a single domain forest. I suspect my problem was caused by my Exchange 2010 server talking to a DC in a different domain in the forest than the one which contained the OU I was aiming for. Hope this helps someone else out.



                BTW - to get the OU format 100% correct for your command, use "Active Directory Users + Computers". On the menu bar: under "view" make sure "Advanced Features" is check marked. Then find the OU you want to use for your default location, on that OU right click and select properties. Go to the "Attribute Editor" tab. scroll down to "distinguishedName" and double click it. Copy the "Value" to your clip board. Use that for your OU switch in the PowerShell command.






                share|improve this answer















                I kept getting the same error message even though my OU designation was 100% correct. I was finally able to set this config in my Exchange 2010.



                Turns out my problem wasn't the formatting of my OU information as all the posts suggested. I have a multi-domain forest. My users (as is the OU I wanted to use for my DistributionGroupDefaultOU) are all in a child domain of the root domain. All my email addresses use the root domain structure. I had the OU information 100% correct using either the OU=, DC=...etc. format or the domain/OU format but still got the error. Frustrating!!! Finally I thought to add the "DomainController" switch to the command pointing to a DC in the child domain and the command was processed successfully! On reflection, the earlier error message had been correct,,, the OU could not be found in the domain (or on the DC) the command (or rather Exchange) was using at the time. When I pointed the command to the correct DC (in the correct domain) the command worked.




                As example, here's what I have:



                • root domain= example.com (DC=Example,DC=com)

                • child domain= staff.example.com ("DC=STAFF,DC=Example,DC=com)

                • all my user accounts are in staff.example.com

                • all email addresses= username@example.com


                • my desired "DistributionGroupDefaultOU"= Groups (in root of staff.example.com)



                  (OU=Groups,DC=STAFF,DC=Example,DC=com)


                Below is what finally worked for me:



                Set-OrganizationConfig -DomainController "DC1.staff.example.com" -DistributionGroupDefaultOU "OU=Groups,DC=STAFF,DC=Example,DC=com"


                Possibly my solution might also work for others having the same problem if they have a single domain forest. I suspect my problem was caused by my Exchange 2010 server talking to a DC in a different domain in the forest than the one which contained the OU I was aiming for. Hope this helps someone else out.



                BTW - to get the OU format 100% correct for your command, use "Active Directory Users + Computers". On the menu bar: under "view" make sure "Advanced Features" is check marked. Then find the OU you want to use for your default location, on that OU right click and select properties. Go to the "Attribute Editor" tab. scroll down to "distinguishedName" and double click it. Copy the "Value" to your clip board. Use that for your OU switch in the PowerShell command.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 15 '15 at 0:35









                masegaloeh

                16.3k74085




                16.3k74085










                answered Jan 14 '15 at 21:17









                RickRick

                1




                1



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Server Fault!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f346699%2fcannot-change-default-ou-for-new-distribution-groups-in-exchange-2010%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                    Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

                    What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company