Grace a l outil Vmware Converter j ai effectue une virtualisation de mon
serveur Exchange 2003 de production. En gros Vmware Converter fais une image
identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange
me signale l erreure suivante : c1041724. J ai essaye de redemarrer les
services Exchange (Aucunes erreure au redemarrage des services), puis quand
il s agit de remonter les banques de donnees voici le resultat de l eventlog
:
----------------------------
Source : MSExchangeSA
Category : MAPI Session
Eventid : 9175
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.
-----------------------
Suivit d un autre eventlog :
---------------------------
Source : SceCli
Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between
account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com.
Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects
(GPOs) could not be resolved to a SID. This error is possibly caused by a
mistyped or deleted user account referenced in either the User Rights or
Restricted Groups branch of a GPO. To resolve this event, contact an
administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find"
%SYSTEMROOT%\Security\Logs\winlogon.log
The string following "Cannot find" in the FIND output identifies the problem
account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This
most likely occurs because the account was deleted, renamed, or is spelled
differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and
Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc
b. Review the results for Computer Configuration\Windows Settings\Security
Settings\Local Policies\User Rights Assignment and Computer
Configuration\Windows Settings\Security Settings\Local Policies\Restricted
Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the
corresponding GPO that contains the problem policy setting is listed under
the column entitled "Source GPO". Note the specific User Rights, Restricted
Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and
click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User
Rights or Restricted Groups that were flagged with a red X in step 2. These
User Rights or Restricted Groups can be corrected by removing or correcting
any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l
active directory de production MAIS dispose d une copie de l active directory
puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m
aider.
Le but de cette virtualisation est de simuler le passage du Service pack 2
Exchange dans un environement de Test totalement identique a celui de la
production.
Cette action est irreversible, confirmez la suppression du commentaire ?
Signaler le commentaire
Veuillez sélectionner un problème
Nudité
Violence
Harcèlement
Fraude
Vente illégale
Discours haineux
Terrorisme
Autre
jalbou
Personne n aurait une idee sur le probleme ? :(
Encore merci
Bonjour,
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon serveur Exchange 2003 de production. En gros Vmware Converter fais une image identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange me signale l erreure suivante : c1041724. J ai essaye de redemarrer les services Exchange (Aucunes erreure au redemarrage des services), puis quand il s agit de remonter les banques de donnees voici le resultat de l eventlog : ---------------------------- Source : MSExchangeSA Category : MAPI Session Eventid : 9175 The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp. -----------------------
Suivit d un autre eventlog : --------------------------- Source : SceCli Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc b. Review the results for Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment and Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted Groups for any errors flagged with a red X. c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE b. From the File menu select "Add/Remove Snap-in..." c. From the "Add/Remove Snap-in" dialog box select "Add..." d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add" e. In the "Select Group Policy Object" dialog box click the "Browse" button. f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l active directory de production MAIS dispose d une copie de l active directory puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m aider. Le but de cette virtualisation est de simuler le passage du Service pack 2 Exchange dans un environement de Test totalement identique a celui de la production.
En vous remerciant.
Personne n aurait une idee sur le probleme ? :(
Encore merci
Bonjour,
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon
serveur Exchange 2003 de production. En gros Vmware Converter fais une image
identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange
me signale l erreure suivante : c1041724. J ai essaye de redemarrer les
services Exchange (Aucunes erreure au redemarrage des services), puis quand
il s agit de remonter les banques de donnees voici le resultat de l eventlog
:
----------------------------
Source : MSExchangeSA
Category : MAPI Session
Eventid : 9175
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.
-----------------------
Suivit d un autre eventlog :
---------------------------
Source : SceCli
Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between
account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com.
Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects
(GPOs) could not be resolved to a SID. This error is possibly caused by a
mistyped or deleted user account referenced in either the User Rights or
Restricted Groups branch of a GPO. To resolve this event, contact an
administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find"
%SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the problem
account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This
most likely occurs because the account was deleted, renamed, or is spelled
differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and
Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc
b. Review the results for Computer ConfigurationWindows SettingsSecurity
SettingsLocal PoliciesUser Rights Assignment and Computer
ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted
Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the
corresponding GPO that contains the problem policy setting is listed under
the column entitled "Source GPO". Note the specific User Rights, Restricted
Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and
click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User
Rights or Restricted Groups that were flagged with a red X in step 2. These
User Rights or Restricted Groups can be corrected by removing or correcting
any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l
active directory de production MAIS dispose d une copie de l active directory
puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m
aider.
Le but de cette virtualisation est de simuler le passage du Service pack 2
Exchange dans un environement de Test totalement identique a celui de la
production.
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon serveur Exchange 2003 de production. En gros Vmware Converter fais une image identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange me signale l erreure suivante : c1041724. J ai essaye de redemarrer les services Exchange (Aucunes erreure au redemarrage des services), puis quand il s agit de remonter les banques de donnees voici le resultat de l eventlog : ---------------------------- Source : MSExchangeSA Category : MAPI Session Eventid : 9175 The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp. -----------------------
Suivit d un autre eventlog : --------------------------- Source : SceCli Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc b. Review the results for Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment and Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted Groups for any errors flagged with a red X. c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE b. From the File menu select "Add/Remove Snap-in..." c. From the "Add/Remove Snap-in" dialog box select "Add..." d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add" e. In the "Select Group Policy Object" dialog box click the "Browse" button. f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l active directory de production MAIS dispose d une copie de l active directory puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m aider. Le but de cette virtualisation est de simuler le passage du Service pack 2 Exchange dans un environement de Test totalement identique a celui de la production.
En vous remerciant.
Thierry DEMAN [MVP]
Bonsoir,
la machine n'a pas changé de nom? ce n'est pas une bonne idée pour un serveur Exchange. Y a t-il d'autres erreurs ou évènements systèmes AVANT le démarrage d'Exchange? L'ancien serveur Exchange d'origine doit rester éteint, bien entendu.
Dans le doute, on peut réinstaller Exchange en mode "disaster recovery" (setup /disasterrecovery)
A+ -- Thierry DEMAN-BARCELÒ MVP Exchange, SQL/Server http://base.faqexchange.info http://www.faqexchange.info http://ISAFirewalls.org "jalbou" a écrit dans le message de news:
Bonjour,
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon serveur Exchange 2003 de production. En gros Vmware Converter fais une image identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange me signale l erreure suivante : c1041724. J ai essaye de redemarrer les services Exchange (Aucunes erreure au redemarrage des services), puis quand il s agit de remonter les banques de donnees voici le resultat de l eventlog : ---------------------------- Source : MSExchangeSA Category : MAPI Session Eventid : 9175 The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp. -----------------------
Suivit d un autre eventlog : --------------------------- Source : SceCli Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc b. Review the results for Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment and Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted Groups for any errors flagged with a red X. c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE b. From the File menu select "Add/Remove Snap-in..." c. From the "Add/Remove Snap-in" dialog box select "Add..." d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add" e. In the "Select Group Policy Object" dialog box click the "Browse" button. f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l active directory de production MAIS dispose d une copie de l active directory puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m aider. Le but de cette virtualisation est de simuler le passage du Service pack 2 Exchange dans un environement de Test totalement identique a celui de la production.
En vous remerciant.
Bonsoir,
la machine n'a pas changé de nom? ce n'est pas une bonne idée pour un
serveur Exchange.
Y a t-il d'autres erreurs ou évènements systèmes AVANT le démarrage
d'Exchange?
L'ancien serveur Exchange d'origine doit rester éteint, bien entendu.
Dans le doute, on peut réinstaller Exchange en mode "disaster recovery"
(setup /disasterrecovery)
A+
--
Thierry DEMAN-BARCELÒ
MVP Exchange, SQL/Server
http://base.faqexchange.info http://www.faqexchange.info
http://ISAFirewalls.org
"jalbou" <jalbou@discussions.microsoft.com> a écrit dans le message de
news:AA0A8FA2-1F72-4D2D-B08B-2A08BD796B5E@microsoft.com...
Bonjour,
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon
serveur Exchange 2003 de production. En gros Vmware Converter fais une
image
identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange
me signale l erreure suivante : c1041724. J ai essaye de redemarrer les
services Exchange (Aucunes erreure au redemarrage des services), puis
quand
il s agit de remonter les banques de donnees voici le resultat de l
eventlog
:
----------------------------
Source : MSExchangeSA
Category : MAPI Session
Eventid : 9175
The MAPI call 'OpenMsgStore' failed with the following error:
The Microsoft Exchange Server computer is not available. Either there are
network problems or the Microsoft Exchange Server computer is down for
maintenance.
The MAPI provider failed.
Microsoft Exchange Server Information Store
ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp.
-----------------------
Suivit d un autre eventlog :
---------------------------
Source : SceCli
Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between
account names and security IDs was done.
Advanced help for this problem is available on
http://support.microsoft.com.
Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects
(GPOs) could not be resolved to a SID. This error is possibly caused by a
mistyped or deleted user account referenced in either the User Rights or
Restricted Groups branch of a GPO. To resolve this event, contact an
administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find"
%SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the
problem
account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined.
This
most likely occurs because the account was deleted, renamed, or is spelled
differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and
Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc
b. Review the results for Computer ConfigurationWindows SettingsSecurity
SettingsLocal PoliciesUser Rights Assignment and Computer
ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted
Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the
corresponding GPO that contains the problem policy setting is listed under
the column entitled "Source GPO". Note the specific User Rights,
Restricted
Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and
click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse"
button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All"
tab
g. For each source GPO identified in step 2, correct the specific User
Rights or Restricted Groups that were flagged with a red X in step 2.
These
User Rights or Restricted Groups can be corrected by removing or
correcting
any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l
active directory de production MAIS dispose d une copie de l active
directory
puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m
aider.
Le but de cette virtualisation est de simuler le passage du Service pack 2
Exchange dans un environement de Test totalement identique a celui de la
production.
la machine n'a pas changé de nom? ce n'est pas une bonne idée pour un serveur Exchange. Y a t-il d'autres erreurs ou évènements systèmes AVANT le démarrage d'Exchange? L'ancien serveur Exchange d'origine doit rester éteint, bien entendu.
Dans le doute, on peut réinstaller Exchange en mode "disaster recovery" (setup /disasterrecovery)
A+ -- Thierry DEMAN-BARCELÒ MVP Exchange, SQL/Server http://base.faqexchange.info http://www.faqexchange.info http://ISAFirewalls.org "jalbou" a écrit dans le message de news:
Bonjour,
Grace a l outil Vmware Converter j ai effectue une virtualisation de mon serveur Exchange 2003 de production. En gros Vmware Converter fais une image identique de la machine et la "virtualise"
Une fois la machine virtuelle en place au lancement de la machine Exchange me signale l erreure suivante : c1041724. J ai essaye de redemarrer les services Exchange (Aucunes erreure au redemarrage des services), puis quand il s agit de remonter les banques de donnees voici le resultat de l eventlog : ---------------------------- Source : MSExchangeSA Category : MAPI Session Eventid : 9175 The MAPI call 'OpenMsgStore' failed with the following error: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. The MAPI provider failed. Microsoft Exchange Server Information Store ID no: 8004011d-0526-00000000
For more information, click http://www.microsoft.com/contentredirect.asp. -----------------------
Suivit d un autre eventlog : --------------------------- Source : SceCli Eventid: 1202
Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%SecurityLogswinlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc b. Review the results for Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesUser Rights Assignment and Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesRestricted Groups for any errors flagged with a red X. c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE b. From the File menu select "Add/Remove Snap-in..." c. From the "Add/Remove Snap-in" dialog box select "Add..." d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add" e. In the "Select Group Policy Object" dialog box click the "Browse" button. f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Il faut savoir que cette machine Exchange n est plus en contact avec l active directory de production MAIS dispose d une copie de l active directory puisqu elle est controleur de domaine secondaire en cas de probleme.
Si vous avez une idee sur le fond du probleme cela pourrait grandement m aider. Le but de cette virtualisation est de simuler le passage du Service pack 2 Exchange dans un environement de Test totalement identique a celui de la production.
