|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Exchange 2003, Outlook 2007 OAB Sync error - 0X8004010FI have recently migrated to a new domain. Any machine that was migrated
using the ADMT tool can replicate the OAB. Any machine joined to domain via Computer properties or newly built receives an OAB Sync error - 0X8004010F. Issue seems to be machine related as one user can login to one machine and download OAB successfully but then logins to a newly joined machine and gets the OAB Sync error - 0X8004010F. Any suggestions? Have you tried deleting the old OAB files? Creating a new Outlook profile?
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Ana" <A**@discussions.microsoft.com> wrote in message news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... >I have recently migrated to a new domain. Any machine that was migrated > using the ADMT tool can replicate the OAB. Any machine joined to domain > via > Computer properties or newly built receives an OAB Sync error - > 0X8004010F. > > Issue seems to be machine related as one user can login to one machine and > download OAB successfully but then logins to a newly joined machine and > gets > the OAB Sync error - 0X8004010F. > Any suggestions? > Have tried on each new machine multiple new profiles, deleting OAB files but
everytime I get this error on any newly joined machine. On a migrated machine I can create any new profile and all users work. It is definitely linked to some rights or something that is not getting created when I join a new machine to the network. Show quoteHide quote "Ed Crowley [MVP]" wrote: > Have you tried deleting the old OAB files? Creating a new Outlook profile? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "Ana" <A**@discussions.microsoft.com> wrote in message > news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... > >I have recently migrated to a new domain. Any machine that was migrated > > using the ADMT tool can replicate the OAB. Any machine joined to domain > > via > > Computer properties or newly built receives an OAB Sync error - > > 0X8004010F. > > > > Issue seems to be machine related as one user can login to one machine and > > download OAB successfully but then logins to a newly joined machine and > > gets > > the OAB Sync error - 0X8004010F. > > Any suggestions? > > > > > Can the newly created profile users connect to public folders?
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Barbara" <Barb***@discussions.microsoft.com> wrote in message news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... > Have tried on each new machine multiple new profiles, deleting OAB files > but > everytime I get this error on any newly joined machine. On a migrated > machine I can create any new profile and all users work. It is definitely > linked to some rights or something that is not getting created when I join > a > new machine to the network. > > "Ed Crowley [MVP]" wrote: > >> Have you tried deleting the old OAB files? Creating a new Outlook >> profile? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "Ana" <A**@discussions.microsoft.com> wrote in message >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... >> >I have recently migrated to a new domain. Any machine that was migrated >> > using the ADMT tool can replicate the OAB. Any machine joined to >> > domain >> > via >> > Computer properties or newly built receives an OAB Sync error - >> > 0X8004010F. >> > >> > Issue seems to be machine related as one user can login to one machine >> > and >> > download OAB successfully but then logins to a newly joined machine and >> > gets >> > the OAB Sync error - 0X8004010F. >> > Any suggestions? >> > >> >> >> Just recreated a new profile on a newly built machine. User can access all
public folders but still receiving the OAB error Show quoteHide quote "Ed Crowley [MVP]" wrote: > Can the newly created profile users connect to public folders? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "Barbara" <Barb***@discussions.microsoft.com> wrote in message > news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... > > Have tried on each new machine multiple new profiles, deleting OAB files > > but > > everytime I get this error on any newly joined machine. On a migrated > > machine I can create any new profile and all users work. It is definitely > > linked to some rights or something that is not getting created when I join > > a > > new machine to the network. > > > > "Ed Crowley [MVP]" wrote: > > > >> Have you tried deleting the old OAB files? Creating a new Outlook > >> profile? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "Ana" <A**@discussions.microsoft.com> wrote in message > >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... > >> >I have recently migrated to a new domain. Any machine that was migrated > >> > using the ADMT tool can replicate the OAB. Any machine joined to > >> > domain > >> > via > >> > Computer properties or newly built receives an OAB Sync error - > >> > 0X8004010F. > >> > > >> > Issue seems to be machine related as one user can login to one machine > >> > and > >> > download OAB successfully but then logins to a newly joined machine and > >> > gets > >> > the OAB Sync error - 0X8004010F. > >> > Any suggestions? > >> > > >> > >> > >> > > > Have you configured an OAB in Exchange 2007 and scheduled its generation?
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Barbara" <Barb***@discussions.microsoft.com> wrote in message news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... > Just recreated a new profile on a newly built machine. User can access > all > public folders but still receiving the OAB error > > "Ed Crowley [MVP]" wrote: > >> Can the newly created profile users connect to public folders? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... >> > Have tried on each new machine multiple new profiles, deleting OAB >> > files >> > but >> > everytime I get this error on any newly joined machine. On a migrated >> > machine I can create any new profile and all users work. It is >> > definitely >> > linked to some rights or something that is not getting created when I >> > join >> > a >> > new machine to the network. >> > >> > "Ed Crowley [MVP]" wrote: >> > >> >> Have you tried deleting the old OAB files? Creating a new Outlook >> >> profile? >> >> -- >> >> Ed Crowley MVP >> >> "There are seldom good technological solutions to behavioral >> >> problems." >> >> .. >> >> >> >> "Ana" <A**@discussions.microsoft.com> wrote in message >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... >> >> >I have recently migrated to a new domain. Any machine that was >> >> >migrated >> >> > using the ADMT tool can replicate the OAB. Any machine joined to >> >> > domain >> >> > via >> >> > Computer properties or newly built receives an OAB Sync error - >> >> > 0X8004010F. >> >> > >> >> > Issue seems to be machine related as one user can login to one >> >> > machine >> >> > and >> >> > download OAB successfully but then logins to a newly joined machine >> >> > and >> >> > gets >> >> > the OAB Sync error - 0X8004010F. >> >> > Any suggestions? >> >> > >> >> >> >> >> >> >> >> >> Its Exchange 2003, did create a new OAB and moved it to our local Exchange
server and replicatd it to our information store only but this did not resolve the issue Show quoteHide quote "Ed Crowley [MVP]" wrote: > Have you configured an OAB in Exchange 2007 and scheduled its generation? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "Barbara" <Barb***@discussions.microsoft.com> wrote in message > news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... > > Just recreated a new profile on a newly built machine. User can access > > all > > public folders but still receiving the OAB error > > > > "Ed Crowley [MVP]" wrote: > > > >> Can the newly created profile users connect to public folders? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... > >> > Have tried on each new machine multiple new profiles, deleting OAB > >> > files > >> > but > >> > everytime I get this error on any newly joined machine. On a migrated > >> > machine I can create any new profile and all users work. It is > >> > definitely > >> > linked to some rights or something that is not getting created when I > >> > join > >> > a > >> > new machine to the network. > >> > > >> > "Ed Crowley [MVP]" wrote: > >> > > >> >> Have you tried deleting the old OAB files? Creating a new Outlook > >> >> profile? > >> >> -- > >> >> Ed Crowley MVP > >> >> "There are seldom good technological solutions to behavioral > >> >> problems." > >> >> .. > >> >> > >> >> "Ana" <A**@discussions.microsoft.com> wrote in message > >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... > >> >> >I have recently migrated to a new domain. Any machine that was > >> >> >migrated > >> >> > using the ADMT tool can replicate the OAB. Any machine joined to > >> >> > domain > >> >> > via > >> >> > Computer properties or newly built receives an OAB Sync error - > >> >> > 0X8004010F. > >> >> > > >> >> > Issue seems to be machine related as one user can login to one > >> >> > machine > >> >> > and > >> >> > download OAB successfully but then logins to a newly joined machine > >> >> > and > >> >> > gets > >> >> > the OAB Sync error - 0X8004010F. > >> >> > Any suggestions? > >> >> > > >> >> > >> >> > >> >> > >> > >> > >> > > > Do you have one on Exchange 2007?
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Barbara" <Barb***@discussions.microsoft.com> wrote in message news:58CE026F-484F-438C-ADB7-5AE8DCD665AE@microsoft.com... > Its Exchange 2003, did create a new OAB and moved it to our local Exchange > server and replicatd it to our information store only but this did not > resolve the issue > > "Ed Crowley [MVP]" wrote: > >> Have you configured an OAB in Exchange 2007 and scheduled its generation? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... >> > Just recreated a new profile on a newly built machine. User can access >> > all >> > public folders but still receiving the OAB error >> > >> > "Ed Crowley [MVP]" wrote: >> > >> >> Can the newly created profile users connect to public folders? >> >> -- >> >> Ed Crowley MVP >> >> "There are seldom good technological solutions to behavioral >> >> problems." >> >> .. >> >> >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... >> >> > Have tried on each new machine multiple new profiles, deleting OAB >> >> > files >> >> > but >> >> > everytime I get this error on any newly joined machine. On a >> >> > migrated >> >> > machine I can create any new profile and all users work. It is >> >> > definitely >> >> > linked to some rights or something that is not getting created when >> >> > I >> >> > join >> >> > a >> >> > new machine to the network. >> >> > >> >> > "Ed Crowley [MVP]" wrote: >> >> > >> >> >> Have you tried deleting the old OAB files? Creating a new Outlook >> >> >> profile? >> >> >> -- >> >> >> Ed Crowley MVP >> >> >> "There are seldom good technological solutions to behavioral >> >> >> problems." >> >> >> .. >> >> >> >> >> >> "Ana" <A**@discussions.microsoft.com> wrote in message >> >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... >> >> >> >I have recently migrated to a new domain. Any machine that was >> >> >> >migrated >> >> >> > using the ADMT tool can replicate the OAB. Any machine joined to >> >> >> > domain >> >> >> > via >> >> >> > Computer properties or newly built receives an OAB Sync error - >> >> >> > 0X8004010F. >> >> >> > >> >> >> > Issue seems to be machine related as one user can login to one >> >> >> > machine >> >> >> > and >> >> >> > download OAB successfully but then logins to a newly joined >> >> >> > machine >> >> >> > and >> >> >> > gets >> >> >> > the OAB Sync error - 0X8004010F. >> >> >> > Any suggestions? >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> We currently don't have any Exchange 2007 server in our environment, only
2003 with 2007 client Show quoteHide quote "Ed Crowley [MVP]" wrote: > Do you have one on Exchange 2007? > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "Barbara" <Barb***@discussions.microsoft.com> wrote in message > news:58CE026F-484F-438C-ADB7-5AE8DCD665AE@microsoft.com... > > Its Exchange 2003, did create a new OAB and moved it to our local Exchange > > server and replicatd it to our information store only but this did not > > resolve the issue > > > > "Ed Crowley [MVP]" wrote: > > > >> Have you configured an OAB in Exchange 2007 and scheduled its generation? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... > >> > Just recreated a new profile on a newly built machine. User can access > >> > all > >> > public folders but still receiving the OAB error > >> > > >> > "Ed Crowley [MVP]" wrote: > >> > > >> >> Can the newly created profile users connect to public folders? > >> >> -- > >> >> Ed Crowley MVP > >> >> "There are seldom good technological solutions to behavioral > >> >> problems." > >> >> .. > >> >> > >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... > >> >> > Have tried on each new machine multiple new profiles, deleting OAB > >> >> > files > >> >> > but > >> >> > everytime I get this error on any newly joined machine. On a > >> >> > migrated > >> >> > machine I can create any new profile and all users work. It is > >> >> > definitely > >> >> > linked to some rights or something that is not getting created when > >> >> > I > >> >> > join > >> >> > a > >> >> > new machine to the network. > >> >> > > >> >> > "Ed Crowley [MVP]" wrote: > >> >> > > >> >> >> Have you tried deleting the old OAB files? Creating a new Outlook > >> >> >> profile? > >> >> >> -- > >> >> >> Ed Crowley MVP > >> >> >> "There are seldom good technological solutions to behavioral > >> >> >> problems." > >> >> >> .. > >> >> >> > >> >> >> "Ana" <A**@discussions.microsoft.com> wrote in message > >> >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... > >> >> >> >I have recently migrated to a new domain. Any machine that was > >> >> >> >migrated > >> >> >> > using the ADMT tool can replicate the OAB. Any machine joined to > >> >> >> > domain > >> >> >> > via > >> >> >> > Computer properties or newly built receives an OAB Sync error - > >> >> >> > 0X8004010F. > >> >> >> > > >> >> >> > Issue seems to be machine related as one user can login to one > >> >> >> > machine > >> >> >> > and > >> >> >> > download OAB successfully but then logins to a newly joined > >> >> >> > machine > >> >> >> > and > >> >> >> > gets > >> >> >> > the OAB Sync error - 0X8004010F. > >> >> >> > Any suggestions? > >> >> >> > > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > Your problem looks like some sort of weird permissions problem, but I don't
have a clue, sorry. -- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "Barbara" <Barb***@discussions.microsoft.com> wrote in message news:4D2CF6BD-280F-44C8-93DA-B75080CA2700@microsoft.com... > We currently don't have any Exchange 2007 server in our environment, only > 2003 with 2007 client > > "Ed Crowley [MVP]" wrote: > >> Do you have one on Exchange 2007? >> -- >> Ed Crowley MVP >> "There are seldom good technological solutions to behavioral problems." >> .. >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> news:58CE026F-484F-438C-ADB7-5AE8DCD665AE@microsoft.com... >> > Its Exchange 2003, did create a new OAB and moved it to our local >> > Exchange >> > server and replicatd it to our information store only but this did not >> > resolve the issue >> > >> > "Ed Crowley [MVP]" wrote: >> > >> >> Have you configured an OAB in Exchange 2007 and scheduled its >> >> generation? >> >> -- >> >> Ed Crowley MVP >> >> "There are seldom good technological solutions to behavioral >> >> problems." >> >> .. >> >> >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> >> news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... >> >> > Just recreated a new profile on a newly built machine. User can >> >> > access >> >> > all >> >> > public folders but still receiving the OAB error >> >> > >> >> > "Ed Crowley [MVP]" wrote: >> >> > >> >> >> Can the newly created profile users connect to public folders? >> >> >> -- >> >> >> Ed Crowley MVP >> >> >> "There are seldom good technological solutions to behavioral >> >> >> problems." >> >> >> .. >> >> >> >> >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message >> >> >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... >> >> >> > Have tried on each new machine multiple new profiles, deleting >> >> >> > OAB >> >> >> > files >> >> >> > but >> >> >> > everytime I get this error on any newly joined machine. On a >> >> >> > migrated >> >> >> > machine I can create any new profile and all users work. It is >> >> >> > definitely >> >> >> > linked to some rights or something that is not getting created >> >> >> > when >> >> >> > I >> >> >> > join >> >> >> > a >> >> >> > new machine to the network. >> >> >> > >> >> >> > "Ed Crowley [MVP]" wrote: >> >> >> > >> >> >> >> Have you tried deleting the old OAB files? Creating a new >> >> >> >> Outlook >> >> >> >> profile? >> >> >> >> -- >> >> >> >> Ed Crowley MVP >> >> >> >> "There are seldom good technological solutions to behavioral >> >> >> >> problems." >> >> >> >> .. >> >> >> >> >> >> >> >> "Ana" <A**@discussions.microsoft.com> wrote in message >> >> >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... >> >> >> >> >I have recently migrated to a new domain. Any machine that was >> >> >> >> >migrated >> >> >> >> > using the ADMT tool can replicate the OAB. Any machine joined >> >> >> >> > to >> >> >> >> > domain >> >> >> >> > via >> >> >> >> > Computer properties or newly built receives an OAB Sync >> >> >> >> > error - >> >> >> >> > 0X8004010F. >> >> >> >> > >> >> >> >> > Issue seems to be machine related as one user can login to one >> >> >> >> > machine >> >> >> >> > and >> >> >> >> > download OAB successfully but then logins to a newly joined >> >> >> >> > machine >> >> >> >> > and >> >> >> >> > gets >> >> >> >> > the OAB Sync error - 0X8004010F. >> >> >> >> > Any suggestions? >> >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Me either! Thanks for your help anyway
Show quoteHide quote "Ed Crowley [MVP]" wrote: > Your problem looks like some sort of weird permissions problem, but I don't > have a clue, sorry. > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "Barbara" <Barb***@discussions.microsoft.com> wrote in message > news:4D2CF6BD-280F-44C8-93DA-B75080CA2700@microsoft.com... > > We currently don't have any Exchange 2007 server in our environment, only > > 2003 with 2007 client > > > > "Ed Crowley [MVP]" wrote: > > > >> Do you have one on Exchange 2007? > >> -- > >> Ed Crowley MVP > >> "There are seldom good technological solutions to behavioral problems." > >> .. > >> > >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> news:58CE026F-484F-438C-ADB7-5AE8DCD665AE@microsoft.com... > >> > Its Exchange 2003, did create a new OAB and moved it to our local > >> > Exchange > >> > server and replicatd it to our information store only but this did not > >> > resolve the issue > >> > > >> > "Ed Crowley [MVP]" wrote: > >> > > >> >> Have you configured an OAB in Exchange 2007 and scheduled its > >> >> generation? > >> >> -- > >> >> Ed Crowley MVP > >> >> "There are seldom good technological solutions to behavioral > >> >> problems." > >> >> .. > >> >> > >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> >> news:B54B17F6-2C44-4A2A-97BD-A7DFA36C69A6@microsoft.com... > >> >> > Just recreated a new profile on a newly built machine. User can > >> >> > access > >> >> > all > >> >> > public folders but still receiving the OAB error > >> >> > > >> >> > "Ed Crowley [MVP]" wrote: > >> >> > > >> >> >> Can the newly created profile users connect to public folders? > >> >> >> -- > >> >> >> Ed Crowley MVP > >> >> >> "There are seldom good technological solutions to behavioral > >> >> >> problems." > >> >> >> .. > >> >> >> > >> >> >> "Barbara" <Barb***@discussions.microsoft.com> wrote in message > >> >> >> news:A7042366-A723-48C0-BE65-BCF3C16D1DDA@microsoft.com... > >> >> >> > Have tried on each new machine multiple new profiles, deleting > >> >> >> > OAB > >> >> >> > files > >> >> >> > but > >> >> >> > everytime I get this error on any newly joined machine. On a > >> >> >> > migrated > >> >> >> > machine I can create any new profile and all users work. It is > >> >> >> > definitely > >> >> >> > linked to some rights or something that is not getting created > >> >> >> > when > >> >> >> > I > >> >> >> > join > >> >> >> > a > >> >> >> > new machine to the network. > >> >> >> > > >> >> >> > "Ed Crowley [MVP]" wrote: > >> >> >> > > >> >> >> >> Have you tried deleting the old OAB files? Creating a new > >> >> >> >> Outlook > >> >> >> >> profile? > >> >> >> >> -- > >> >> >> >> Ed Crowley MVP > >> >> >> >> "There are seldom good technological solutions to behavioral > >> >> >> >> problems." > >> >> >> >> .. > >> >> >> >> > >> >> >> >> "Ana" <A**@discussions.microsoft.com> wrote in message > >> >> >> >> news:F7DE759A-4121-4513-8F74-32855FB31793@microsoft.com... > >> >> >> >> >I have recently migrated to a new domain. Any machine that was > >> >> >> >> >migrated > >> >> >> >> > using the ADMT tool can replicate the OAB. Any machine joined > >> >> >> >> > to > >> >> >> >> > domain > >> >> >> >> > via > >> >> >> >> > Computer properties or newly built receives an OAB Sync > >> >> >> >> > error - > >> >> >> >> > 0X8004010F. > >> >> >> >> > > >> >> >> >> > Issue seems to be machine related as one user can login to one > >> >> >> >> > machine > >> >> >> >> > and > >> >> >> >> > download OAB successfully but then logins to a newly joined > >> >> >> >> > machine > >> >> >> >> > and > >> >> >> >> > gets > >> >> >> >> > the OAB Sync error - 0X8004010F. > >> >> >> >> > Any suggestions? > >> >> >> >> > > >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> > >> >> > >> >> > >> > >> > >> > > > 
Other interesting topics
Exchg 2003 Messages? Where located?
event id 467 Exchange 2003 Restore / Recovery on SBS 2003 Outgoing SMPT Exchange responding slow to Outlook Clients exchange 2003 distribution group fails to create an email address Re: Ex07 Info store intermittently stopping. Group Rights problem Exchange Server 2003 Mainstream Support Exchange Multiple Raid Array |
|||||||||||||||||||||||
