| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#1
| |||
| |||
| hello all, I have a newly installed exchange 2003 server with public folder replication failing and recipient policy errors. During the initial setup the server was installed in the incorrect administrative group, uninstalled and then reinstalled in the correct group. However we have now completed the migration only to find that new users are assigned addresses from the wrong recipient policy and public folder replication fails. The public folder attributes (using adsiedit) show email addresses relating to the other admin group. Does anyone have any recomendations? Currently we are considering re-installing but as this didn't avoid the problem first time around we are reluctant to go ahead. All advice is welcomed, Simon. |
|
#2
| |||
| |||
| Hi, I can't see how the placement of server into an administrative group has any relation to the recipient policies. I would start by making sure that the recipient policies have the desired LDAP filter and that it finds the correct users when using the filter. Could you explain how you configured the policy to take the administrative group into account (and post the filter you are using)? Leif "Simon" <reply@togroup.com> wrote in message news:%236iYuma1GHA.5048@TK2MSFTNGP05.phx.gbl... > hello all, > > I have a newly installed exchange 2003 server with public folder > replication failing and recipient policy errors. > > During the initial setup the server was installed in the incorrect > administrative group, uninstalled and then reinstalled in the correct > group. > > However we have now completed the migration only to find that new users > are assigned addresses from the wrong recipient policy and public folder > replication fails. The public folder attributes (using adsiedit) show > email addresses relating to the other admin group. > > Does anyone have any recomendations? Currently we are considering > re-installing but as this didn't avoid the problem first time around we > are reluctant to go ahead. All advice is welcomed, Simon. > |
|
#3
| |||
| |||
| I believe my error in first installing the server into the incorrect admin group is irrelevant. this problem is entirely doen to recipient policy settings. We have not set up a new recipient policy for the new server yet... Is there an article outling the procedure when setting up a new policy. Will the public folder addresses be recreated when we add a new policy? Many thanks for your help, Simon "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message news:%23lhHRsd1GHA.3752@TK2MSFTNGP02.phx.gbl... > Hi, > > I can't see how the placement of server into an administrative group has > any relation to the recipient policies. > > I would start by making sure that the recipient policies have the desired > LDAP filter and that it finds the correct users when using the filter. > > Could you explain how you configured the policy to take the administrative > group into account (and post the filter you are using)? > > Leif > > "Simon" <reply@togroup.com> wrote in message > news:%236iYuma1GHA.5048@TK2MSFTNGP05.phx.gbl... >> hello all, >> >> I have a newly installed exchange 2003 server with public folder >> replication failing and recipient policy errors. >> >> During the initial setup the server was installed in the incorrect >> administrative group, uninstalled and then reinstalled in the correct >> group. >> >> However we have now completed the migration only to find that new users >> are assigned addresses from the wrong recipient policy and public folder >> replication fails. The public folder attributes (using adsiedit) show >> email addresses relating to the other admin group. >> >> Does anyone have any recomendations? Currently we are considering >> re-installing but as this didn't avoid the problem first time around we >> are reluctant to go ahead. All advice is welcomed, Simon. >> > > |
|
#4
| |||
| |||
| Hi, This article explains how to create recipient policies: http://www.msexchange.org/tutorials/MF010.html I don't think that the addresses of the public folders matters - you need to troublshoot the replication using this: http://support.microsoft.com/default...b;en-us;842273 Leif "Simon" <reply@togroup.com> wrote in message news:%23lyAP8m1GHA.4796@TK2MSFTNGP03.phx.gbl... >I believe my error in first installing the server into the incorrect admin >group is irrelevant. this problem is entirely doen to recipient policy >settings. > > We have not set up a new recipient policy for the new server yet... Is > there an article outling the procedure when setting up a new policy. Will > the public folder addresses be recreated when we add a new policy? > > Many thanks for your help, Simon > > "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message > news:%23lhHRsd1GHA.3752@TK2MSFTNGP02.phx.gbl... >> Hi, >> >> I can't see how the placement of server into an administrative group has >> any relation to the recipient policies. >> >> I would start by making sure that the recipient policies have the desired >> LDAP filter and that it finds the correct users when using the filter. >> >> Could you explain how you configured the policy to take the >> administrative group into account (and post the filter you are using)? >> >> Leif >> >> "Simon" <reply@togroup.com> wrote in message >> news:%236iYuma1GHA.5048@TK2MSFTNGP05.phx.gbl... >>> hello all, >>> >>> I have a newly installed exchange 2003 server with public folder >>> replication failing and recipient policy errors. >>> >>> During the initial setup the server was installed in the incorrect >>> administrative group, uninstalled and then reinstalled in the correct >>> group. >>> >>> However we have now completed the migration only to find that new users >>> are assigned addresses from the wrong recipient policy and public folder >>> replication fails. The public folder attributes (using adsiedit) show >>> email addresses relating to the other admin group. >>> >>> Does anyone have any recomendations? Currently we are considering >>> re-installing but as this didn't avoid the problem first time around we >>> are reluctant to go ahead. All advice is welcomed, Simon. >>> >> >> > > |
|
#5
| |||
| |||
| having read the articles you recommended we have setup a recipient policy and a recipient update service for the new exchange 2003 server. After requesting a rebuild and also update now the public folder attributes have not updating and therefore replication is still not taking place. I have read around the subject but apart from manually changing the entires using ADSIEDIT I haven't found a solution, Have I missed something? Many thanks for all your help, Simon. "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message news:utflIRq1GHA.4228@TK2MSFTNGP06.phx.gbl... > Hi, > > This article explains how to create recipient policies: > http://www.msexchange.org/tutorials/MF010.html > > I don't think that the addresses of the public folders matters - you need > to troublshoot the replication using this: > http://support.microsoft.com/default...b;en-us;842273 > > Leif > > "Simon" <reply@togroup.com> wrote in message > news:%23lyAP8m1GHA.4796@TK2MSFTNGP03.phx.gbl... >>I believe my error in first installing the server into the incorrect admin >>group is irrelevant. this problem is entirely doen to recipient policy >>settings. >> >> We have not set up a new recipient policy for the new server yet... Is >> there an article outling the procedure when setting up a new policy. Will >> the public folder addresses be recreated when we add a new policy? >> >> Many thanks for your help, Simon >> >> "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message >> news:%23lhHRsd1GHA.3752@TK2MSFTNGP02.phx.gbl... >>> Hi, >>> >>> I can't see how the placement of server into an administrative group has >>> any relation to the recipient policies. >>> >>> I would start by making sure that the recipient policies have the >>> desired LDAP filter and that it finds the correct users when using the >>> filter. >>> >>> Could you explain how you configured the policy to take the >>> administrative group into account (and post the filter you are using)? >>> >>> Leif >>> >>> "Simon" <reply@togroup.com> wrote in message >>> news:%236iYuma1GHA.5048@TK2MSFTNGP05.phx.gbl... >>>> hello all, >>>> >>>> I have a newly installed exchange 2003 server with public folder >>>> replication failing and recipient policy errors. >>>> >>>> During the initial setup the server was installed in the incorrect >>>> administrative group, uninstalled and then reinstalled in the correct >>>> group. >>>> >>>> However we have now completed the migration only to find that new users >>>> are assigned addresses from the wrong recipient policy and public >>>> folder replication fails. The public folder attributes (using adsiedit) >>>> show email addresses relating to the other admin group. >>>> >>>> Does anyone have any recomendations? Currently we are considering >>>> re-installing but as this didn't avoid the problem first time around we >>>> are reluctant to go ahead. All advice is welcomed, Simon. >>>> >>> >>> >> >> > > |
|
#6
| |||
| |||
| Hi, Did you try to troubleshoot the public folder replication as mentioned in my previous post? Leif "Simon" <reply@togroup.com> wrote in message news:ui8s1my1GHA.4392@TK2MSFTNGP04.phx.gbl... > having read the articles you recommended we have setup a recipient policy > and a recipient update service for the new exchange 2003 server. After > requesting a rebuild and also update now the public folder attributes have > not updating and therefore replication is still not taking place. > > I have read around the subject but apart from manually changing the > entires using ADSIEDIT I haven't found a solution, > > Have I missed something? Many thanks for all your help, Simon. > > "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message > news:utflIRq1GHA.4228@TK2MSFTNGP06.phx.gbl... >> Hi, >> >> This article explains how to create recipient policies: >> http://www.msexchange.org/tutorials/MF010.html >> >> I don't think that the addresses of the public folders matters - you need >> to troublshoot the replication using this: >> http://support.microsoft.com/default...b;en-us;842273 >> >> Leif >> >> "Simon" <reply@togroup.com> wrote in message >> news:%23lyAP8m1GHA.4796@TK2MSFTNGP03.phx.gbl... >>>I believe my error in first installing the server into the incorrect >>>admin group is irrelevant. this problem is entirely doen to recipient >>>policy settings. >>> >>> We have not set up a new recipient policy for the new server yet... Is >>> there an article outling the procedure when setting up a new policy. >>> Will the public folder addresses be recreated when we add a new policy? >>> >>> Many thanks for your help, Simon >>> >>> "Leif Pedersen [MVP]" <Leif.pedersenNO-SPAM@get2net.dk> wrote in message >>> news:%23lhHRsd1GHA.3752@TK2MSFTNGP02.phx.gbl... >>>> Hi, >>>> >>>> I can't see how the placement of server into an administrative group >>>> has any relation to the recipient policies. >>>> >>>> I would start by making sure that the recipient policies have the >>>> desired LDAP filter and that it finds the correct users when using the >>>> filter. >>>> >>>> Could you explain how you configured the policy to take the >>>> administrative group into account (and post the filter you are using)? >>>> >>>> Leif >>>> >>>> "Simon" <reply@togroup.com> wrote in message >>>> news:%236iYuma1GHA.5048@TK2MSFTNGP05.phx.gbl... >>>>> hello all, >>>>> >>>>> I have a newly installed exchange 2003 server with public folder >>>>> replication failing and recipient policy errors. >>>>> >>>>> During the initial setup the server was installed in the incorrect >>>>> administrative group, uninstalled and then reinstalled in the correct >>>>> group. >>>>> >>>>> However we have now completed the migration only to find that new >>>>> users are assigned addresses from the wrong recipient policy and >>>>> public folder replication fails. The public folder attributes (using >>>>> adsiedit) show email addresses relating to the other admin group. >>>>> >>>>> Does anyone have any recomendations? Currently we are considering >>>>> re-installing but as this didn't avoid the problem first time around >>>>> we are reluctant to go ahead. All advice is welcomed, Simon. >>>>> >>>> >>>> >>> >>> >> >> > > |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.