Scenarium

 Logg inn       Registrer
Velkommen!
Minimer
(1) Opprett din bruker
(2) Logg på webstedet
(3) Still ditt spørsmål
 
PS: Du må ikke betale for å stille spørsmål i forumet. men du må være registrert medlem av forumet.

Privat post
Privat post

I dette vinduet finner du din private post.

Du må være logget inn for å bruke denne tjenesten.
STENGT
STENGT
Minimer
Dette forumet er stengt. Eksisterende abonnenter kan logge på og hente artikler. Det er lovet en artikkel serie om Remote Desktop Services som vil bli skrevet og lagt ut for abonnenter. Webstedet er til salgs, og vil opphøre å eksistere i en gang mars 2013.
Forum
Forum
Ubesvarte Aktive Emner Forums Søk
Forums > Microsoft Small Business Server 2008 > Small Business Server 2008 Premium Servertest
Migrering
Siste Postering 12-10-2010 09:53 av Dag Staale Jenssen. 12 Svar.
Utskriftsvennlig
Sortering:
PrevPrev NesteNeste
Du er ikke autorisert til å svare.
Forfatter Meldinger Løst
SN-LRSBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:6
Avatar

--
11-02-2009 04:10  

Hei.

Spørsmål i forbindelse med migrering fra SMB 2003 til SMB 2008.

Må alle wizardene kjøres i oppsatt rekkefølge eller kan noen tas senere etter 21-dagers fristen? Tenker da først og fremst på de som er obligatoriske.

Holder for tiden på med migreringsprosessen og får feilmelding i forbindelse med prosedyren "Configure the Internet adress". Feilmeldingen kommer på første delen som omhandler remote-funksjonen. Har eksternt domene og DNS skal være satt opp riktig ifølge folkene på webhotellet som vi bruker. Exchange-delen i wizarden kommer ut OK. Warningdetails viser at det mangler porter i ruteren. Har lagt inn portforwarding på portene som er listet opp i veiledningen, og finner ut at disse er åpne. Har en Zyxel Zywall 2 ruter som hittil har fungert bra hos oss. Kanskje den skulle vært byttet?  Er det noen hint om hva årsaken kan være?
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
12-02-2009 07:35  
Hei!
Joda, det er komponenter som kan gjøres i ulik rekkefølge. Men du må utvise dyp forståelse for valget og utsettelsene!!!!!
Kan du legge inn den konkrete feilmeldingen du får, jeg er usikker på hva du egentlig har gjort og hvorfor du får en feilmelding. Vær nøye.
Så til et meget godt råd:
Påse at at all GPO har gått inn på alle arbeidstasjoner, i særdeleshet gjelder det forlder redirection, før du fjerner den gamle serveren (dcpromo). Sjekk denne feilmeldingen jeg sliter med etter siste migrering:
Event ID 502
Kunne ikke aktivere policy og omadressere mappen Music til \\SBS02\RedirectedFolders\Dag Staale Jenssen\My Documents\My Music.
 Alternativer for omadressering=80009231.
 Følgende feil oppstod: Kan ikke omadressere fordi kildemappen \\SBS01\Users\Dag Staale Jenssen\My Documents\My Music er frakoblet.
 Feilinformasjon: Nettverksbanen ble ikke funnet.
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
SN-LRSBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:6
Avatar

--
12-02-2009 08:27  

Hei og takk for svar.

Feilmeldingen som kommer lyder som følger.

"The server cannot configure Remote Web Workplace. To correct this prblem, run the Fix My Network Wizard."

Har tillat meg å prøve det også uten at det hjalp noe.

Svein
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
12-02-2009 08:56  
Dette trenger ikke å være et stort problem, men det er en indikasjon på at noe er feil i forbindelse med IIS. Kan det være at du har dette problemet som beskrives her (sjekk Certificate authority name): http://blog.mpecsinc.ca/2008/08/sbs...emote.html
 
Jeg hadde nok prioritert å løse dette problemet før jeg føk videre.
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
12-02-2009 09:02  
Migreringsartikkelen inneholder en oversikt over logger på SBS 2008. Kan du gå inn å finne den konkrete feilmeldingen i den aktuelle loggen. Kan du også sjekke installasjonlogg eventuelt andre logger for eventuelle feil?
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
12-02-2009 09:08  
Kan du sjekke om RWW fungere fra internett?
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
SN-LRSBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:6
Avatar

--
13-02-2009 02:27  

Får opp innloggingsbildet til RWW fra internett, men kommer ikke videre ved innlogging. Nestebilde viser kun melding, "cannot connect to RWW"

Fra installasjonsloggen får jeg 2 feilmeldinger. "Windows small business server group policies cannot be configured" samt Windows server update Services cannot be configured".

Når det gjelder answer file stod dette feltet tomt og det skulle vel bety at feilen ikke ligger der, men ved gjennomgang av loggfilen DPCW ser jeg at ved første gangs kjøring av wizarden har jeg skrevet feil og lagt inn vårt lokale domene i adressefeltet. (eg. remote.domene.local). Om dette kan være årsaken vet jeg ikke.  Forsøkte wizarden pånytt idag og siste del av loggen ser slik ut: [3628] 090213.122702.2701: CoreNet: Exception System.Runtime.InteropServices.COMException:
HR: -2147220618

[3628] 090213.122702.2701: Exception:
---------------------------------------
An exception of type 'Type: System.Runtime.InteropServices.COMException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 02/13/2009 12:27:02
Message: Exception from HRESULT: 0x80040376
Stack:    at Microsoft.WindowsServerSolutions.UPnPLib.Interop.IUPnPService.InvokeAction(String bstrActionName, Object vInActionArgs, Object& pvOutActionArgs)
    at Microsoft.WindowsServerSolutions.CoreNetworking.RouterProviders.UpnpRouter.AddPortMapping(PortMapping pm)

[3628] 090213.122702.2701: CoreNet: WANIPConnection:1::AddPortMapping() returned an unexpected result
[3628] 090213.122702.2857: AdminTME: Status: TaskId = Networking.Wizards.NetSvcWizard.ConfigureRouter, RootTaskId = Networking.Wizards.NetSvcWizard.ConfigureRouter, Success: False, Warning: True, Continue: True, Message: Windows Small Business Server 2008 cannot open ports 25, 80, 443, and 987 to the IP address of the server. In order to receive e-mail and other information over the Internet, you must manually open the ports. To manually open the ports, see the documentation from your router manufacturer.
[8920] 090213.122702.2857: AdminTME: Committer: Completed called
[8920] 090213.122702.2857: AdminTME: Committer: Committer Completed.

 
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
13-02-2009 06:03  
Kan du ordne så jeg kan logge på server med RDP?
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
SN-LRSBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:6
Avatar

--
13-02-2009 06:38  

Ok.
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
13-02-2009 11:38  
Hei!
 
Jeg har tatt en rask tur gjennom de to servere for å titte på problemstillingen i det dette er interessant. Min gjennomgang har avdekket følgende:
 
1)      Under basis installasjonen av SBS 2008 har det inntruffet et forhold som installasjonsrutinen ikke greide å takle. Replikeringen mellom de to domain controllere to uventet lang tid. Du fikk varsel og spørsmål under veis, der serveren fortalte deg at det tok lang tid og den spurte deg om du ville vente. Første gang valgte du å vente, den neste gangen du ble spurt avbørt du. Ved dette fortsatte installasjonene. Når installasjonen var ferdig fikk du to advarsler:
 
·         ConfigureGP: Windows Small Business Server group policies cannot be configured.
·         WSUSConfig: Windows Server Update Services cannot be configured.
 
2)      Jeg har undersøkt SBSSetup loggen. I loggen kan vi se at replikeringen mellom SBS 2003 og 2008 har hat problemer, og at replikeringen ikke var vellykket.  Utdrag av loggfilen er vedlagt.
 
3)      Jeg gikk derfor over til SBS 2003 serveren for å lete etter mulige årsaker som kan påvire replikeringen. For å gjøre en første test benyttet jeg DCDIAG. Denne rapporterte om feil i loggfilene i de siste 24 timer. Jeg undersøkte derfor loggfilene nærmere og fant det som muligens kan ha forårsaket problemet. På denne serveren har du hatt feilmeldinger knyttet til NtFRS siden 04.11.2006. Feilmeldingene er vedlagt. Ikke uventet gjelder feilmeldingen replikering som ikke kan gjennomførers. Det må også nevnes at disse feilmeldingene har tikket inn minst en gang om dagen siden 2006.
 
4)      De etterfølgende feilmeldinger som over nevnt mener jeg er følge feil av det opprinnelige problemet som har eksistert på SBS 2003 siden 2006.
 
5)      Slik jeg ser dette har du to valg:
 
a)      Kontakt Microsoft Product Support og hør om de kan fikse problemet. Jeg ser ikke bort fra at de på et vis kan greie å løse det. Jeg greier det ikke.
 
b)      Reinstaller SBS 2008.
 
6)      Det er flere veien til Rom. Her er en av dem. Dersom du velger å reinstallere SBS 2008, bør du som første punkt sørge for verifiserte sikkerhetskopier av data på SBS 2003. Deretter kjører du shutdown på SBS 2008, og kobler denne serveren fra nettverket. Monter en hjelpe ruter i SBS 2003 nettverket og gi WAN porten en ip adresse i dette Lan. Monter så SBS 2008 i ruteren Lan port som må konfigureres med et annet subbnett en nettverket til SBS 2003. Reinstaller deretter SBS 2008. Når installasjonen av SBS 2008 er ferdig, legg inn sikkerhetskopier fra SBS 2003. Når sikkerhetskopier er verifisert, kjør shudwon på SBS 2003 og kobl denne serveren fra nettverket. Kobl så SBS 2008 inn i det gamle nettverket etter at du har stil rutterens Lan med samme ip adresse (subbnett) som du hadde på hjelperuteren. La meg presisere at en hjelperuter kun er nødvendig dersom du skal ha SBS 2003 oppretiv frem til det tidspunkt SBS 2008 er klar. 
 
 
 
FEILMEDLINGER FRA NtFRS LOGGEN PÅ SBS 2003
Event Type:       Error
Event Source:   NtFrs
Event Category:               None
Event ID:             13555
Date:                    04.11.2006
Time:                    15:36:51
User:                    N/A
Computer:         SERVERLRS
Description:
The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on this computer until the following recovery steps are performed:
 
 Recovery Steps:
 
 [1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:
 
    net stop ntfrs
    net start ntfrs
 
If this fails to clear up the problem then proceed as follows.
 
 [2] For Active Directory Domain Controllers that DO NOT host any DFS alternates or other replica sets with replication enabled:
 
If there is at least one other Domain Controller in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
 
If there are NO other Domain Controllers in this domain then restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and choose the Advanced option which marks the sysvols as primary.
 
If there are other Domain Controllers in this domain but ALL of them have this event log message then restore one of them as primary (data files from primary will replicate everywhere) and the others as non-authoritative.  
 
 [3] For Active Directory Domain Controllers that host DFS alternates or other replica sets with replication enabled:
 
 (3-a) If the Dfs alternates on this DC do not have any other replication partners then copy the data under that Dfs share to a safe location.
 (3-b) If this server is the only Active Directory Domain Controller for this domain then, before going to (3-c), make sure this server does not have any inbound or outbound connections to other servers that were formerly Domain Controllers for this domain but are now off the net (and will never be coming back online) or have been fresh installed without being demoted. To delete connections use the Sites and Services snapin and look for
Sites->NAME_OF_SITE->Servers->NAME_OF_SERVER->NTDS Settings->CONNECTIONS.
 (3-c) Restore the "system state" of this DC from backup (using ntbackup or other backup-restore utility) and make it non-authoritative.
 (3-d) Copy the data from step (3-a) above to the original location after the sysvol share is published.  
 
 [4] For other Windows servers:
 
 (4-a) If any of the DFS alternates or other replica sets hosted by this server do not have any other replication partners then copy the data under its share or replica tree root to a safe location.
 (4-b) net stop ntfrs
 (4-c) rd /s /q c:\windows\ntfrs\jet
 (4-d) net start ntfrs
 (4-e) Copy the data from step (4-a) above to the original location after the service has initialized (5 minutes is a safe waiting time).
 
Note: If this error message is in the eventlog of all the members of a particular replica set then perform steps (4-a) and (4-e) above on only one of the members.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp.
 
 
Event Type:       Error
Event Source:   NtFrs
Event Category:               None
Event ID:             13552
Date:                    05.11.2006
Time:                    15:41:37
User:                    N/A
Computer:         SERVERLRS
Description:
The File Replication Service is unable to add this computer to the following replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
This could be caused by a number of problems such as:
 -- an invalid root path,
 -- a missing directory,
 -- a missing disk volume,
 -- a file system on the volume that does not support NTFS 5.0
 
The information below may help to resolve the problem:
Computer DNS name is "serverlrs.LRS.local"
Replica set member name is "SERVERLRS"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
Windows error status code is 
FRS error status code is FrsErrorMismatchedJournalId
 
Other event log messages may also help determine the problem. Correct the problem and the service will attempt to restart replication automatically at a later time.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp.
 
Event Type:       Warning
Event Source:   NtFrs
Event Category:               None
Event ID:             13562
Date:                    15.11.2006
Time:                    09:29:10
User:                    N/A
Computer:         SERVERLRS
Description:
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller serverlrs.LRS.local for FRS replica set configuration information.
 
 Could not find computer object for this computer. Will try again at next polling cycle. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp." target="_blank" rel="nofollow">http://go.microsoft.com/fwlink/events.asp.
 
UTDRAG FRA SBSSETUP LOGFILEN PÅ SBS 2008
[1596] 090202.022033.6312: Task: Running Task("PostDCPromoTask") with TaskProcessor("NET").
[1596] 090202.022033.8026: Task: Making server a global catalog
[1596] 090202.022033.9740: Task: Waiting for isGlobalCatalogReady attribute in LDAP://SERVERLRS2.LRS.local/rootdse
[1596] 090202.022534.0276: Task: We are now a global catalog
[1596] 090202.022534.0276: Task: Taking all FSMO roles.
[1596] 090202.022534.5112: Task: Current machine now has the following roles:
[1596] 090202.022534.5112: Task: SchemaRole
[1596] 090202.022534.5268: Task: NamingRole
[1596] 090202.022534.5268: Task: PdcRole
[1596] 090202.022534.5268: Task: RidRole
[1596] 090202.022534.5268: Task: InfrastructureRole
[1596] 090202.022534.5424: Task: Waiting for replication to finish
[1596] 090202.023034.5467: Task:            Finished waiting.
[1596] 090202.023034.5467: Setup: DsGetDcName returned: 0
[1596] 090202.023034.5467: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.023034.5467: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.023034.6403: Task:            There are 0 pending replication operations.
[1596] 090202.023034.6715: Setup:         Attempting LDAP bind.
[1596] 090202.023034.6715: Setup:         Bind failed with: A local error occurred.
[1596] 090202.023034.6715: Task: Waiting for replication to finish
[1596] 090202.023534.6771: Task:            Finished waiting.
[1596] 090202.023534.6771: Setup: DsGetDcName returned: 0
[1596] 090202.023534.6771: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.023534.6771: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.023534.6927: Task:            There are 0 pending replication operations.
[1596] 090202.023534.6927: Setup:         Attempting LDAP bind.
[1596] 090202.023534.6927: Setup:         Bind failed with: A local error occurred.
[1596] 090202.023534.6927: Task: Waiting for replication to finish
[1596] 090202.024034.6982: Task:            Finished waiting.
[1596] 090202.024034.6982: Setup: DsGetDcName returned: 0
[1596] 090202.024034.6982: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.024034.6982: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.024034.6982: Task:            There are 0 pending replication operations.
[1596] 090202.024034.6982: Setup:         Attempting LDAP bind.
[1596] 090202.024034.6982: Setup:         Bind failed with: A local error occurred.
[1596] 090202.024034.6982: Task: Waiting for replication to finish
[1596] 090202.024534.7037: Task:            Finished waiting.
[1596] 090202.024534.7037: Setup: DsGetDcName returned: 0
[1596] 090202.024534.7037: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.024534.7037: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.024534.7193: Task:            There are 0 pending replication operations.
[1596] 090202.024534.7193: Setup:         Attempting LDAP bind.
[1596] 090202.024534.7193: Setup:         Bind failed with: A local error occurred.
[1596] 090202.024534.7193: Task: Waiting for replication to finish
[1596] 090202.025034.7248: Task:            Finished waiting.
[1596] 090202.025034.7248: Setup: DsGetDcName returned: 0
[1596] 090202.025034.7248: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.025034.7248: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.025034.7404: Task:            There are 0 pending replication operations.
[1596] 090202.025034.7404: Setup:         Attempting LDAP bind.
[1596] 090202.025034.7404: Setup:         Bind successful
[1596] 090202.065207.0899: Task: Waiting for replication to finish
[1596] 090202.065707.0766: Task:            Finished waiting.
[1596] 090202.065707.0766: Setup: DsGetDcName returned: 0
[1596] 090202.065707.0766: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.065707.0766: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.065707.0766: Task:            There are 0 pending replication operations.
[1596] 090202.065707.0766: Setup:         Attempting LDAP bind.
[1596] 090202.065707.0922: Setup:         Bind successful
[1596] 090202.065707.0922: Task: Waiting for replication to finish
[1596] 090202.070207.0901: Task:            Finished waiting.
[1596] 090202.070207.0901: Setup: DsGetDcName returned: 0
[1596] 090202.070207.0901: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.070207.0901: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.070207.0901: Task:            There are 0 pending replication operations.
[1596] 090202.070207.0901: Setup:         Attempting LDAP bind.
[1596] 090202.070207.0901: Setup:         Bind successful
[1596] 090202.070207.0901: Task: Waiting for replication to finish
[1596] 090202.070707.0879: Task:            Finished waiting.
[1596] 090202.070707.0879: Setup: DsGetDcName returned: 0
[1596] 090202.070707.0879: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.070707.0879: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.070707.0879: Task:            There are 0 pending replication operations.
[1596] 090202.070707.0879: Setup:         Attempting LDAP bind.
[1596] 090202.070707.0879: Setup:         Bind successful
[1596] 090202.070707.0879: Task: Waiting for replication to finish
[1596] 090202.071207.0746: Task:            Finished waiting.
[1596] 090202.071207.0746: Setup: DsGetDcName returned: 0
[1596] 090202.071207.0746: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.071207.0746: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.071207.0746: Task:            There are 0 pending replication operations.
[1596] 090202.071207.0746: Setup:         Attempting LDAP bind.
[1596] 090202.071207.0746: Setup:         Bind successful
[1596] 090202.071207.0746: Task: Waiting for replication to finish
[1596] 090202.071707.0725: Task:            Finished waiting.
[1596] 090202.071707.0725: Setup: DsGetDcName returned: 0
[1596] 090202.071707.0725: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.071707.0725: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.071707.0725: Task:            There are 0 pending replication operations.
[1596] 090202.071707.0725: Setup:         Attempting LDAP bind.
[1596] 090202.071707.0881: Setup:         Bind successful
[1596] 090202.071721.7830: Task: Waiting for replication to finish
[1596] 090202.072221.7808: Task:            Finished waiting.
[1596] 090202.072221.7808: Setup: DsGetDcName returned: 0
[1596] 090202.072221.7808: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.072221.7808: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.072221.7808: Task:            There are 0 pending replication operations.
[1596] 090202.072221.7808: Setup:         Attempting LDAP bind.
[1596] 090202.072221.7808: Setup:         Bind successful
[1596] 090202.072221.7808: Task: Waiting for replication to finish
[1596] 090202.072721.7681: Task:            Finished waiting.
[1596] 090202.072721.7681: Setup: DsGetDcName returned: 0
[1596] 090202.072721.7681: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.072721.7681: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.072721.7681: Task:            There are 0 pending replication operations.
[1596] 090202.072721.7681: Setup:         Attempting LDAP bind.
[1596] 090202.072721.7681: Setup:         Bind successful
[1596] 090202.072721.7681: Task: Waiting for replication to finish
[1596] 090202.073221.7654: Task:            Finished waiting.
[1596] 090202.073221.7654: Setup: DsGetDcName returned: 0
[1596] 090202.073221.7654: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.073221.7654: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.073221.7654: Task:            There are 0 pending replication operations.
[1596] 090202.073221.7654: Setup:         Attempting LDAP bind.
[1596] 090202.073221.7654: Setup:         Bind successful
[1596] 090202.073221.7654: Task: Waiting for replication to finish
[1596] 090202.073721.7632: Task:            Finished waiting.
[1596] 090202.073721.7632: Setup: DsGetDcName returned: 0
[1596] 090202.073721.7632: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.073721.7632: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.073721.7632: Task:            There are 0 pending replication operations.
[1596] 090202.073721.7632: Setup:         Attempting LDAP bind.
[1596] 090202.073721.7632: Setup:         Bind successful
[1596] 090202.073721.7632: Task: Waiting for replication to finish
[1596] 090202.074221.7611: Task:            Finished waiting.
[1596] 090202.074221.7611: Setup: DsGetDcName returned: 0
[1596] 090202.074221.7611: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.074221.7611: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.074221.7611: Task:            There are 0 pending replication operations.
[1596] 090202.074221.7611: Setup:         Attempting LDAP bind.
[1596] 090202.074221.7611: Setup:         Bind successful
[1596] 090202.074934.6728: Task: Waiting for replication to finish
[1596] 090202.075434.6707: Task:            Finished waiting.
[1596] 090202.075434.6707: Setup: DsGetDcName returned: 0
[1596] 090202.075434.6707: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.075434.6707: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.075434.6707: Task:            There are 0 pending replication operations.
[1596] 090202.075434.6707: Setup:         Attempting LDAP bind.
[1596] 090202.075434.6863: Setup:         Bind successful
[1596] 090202.075434.6863: Task: Waiting for replication to finish
[1596] 090202.075934.6841: Task:            Finished waiting.
[1596] 090202.075934.6841: Setup: DsGetDcName returned: 0
[1596] 090202.075934.6841: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.075934.6841: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.075934.6841: Task:            There are 0 pending replication operations.
[1596] 090202.075934.6841: Setup:         Attempting LDAP bind.
[1596] 090202.075934.6841: Setup:         Bind successful
[1596] 090202.075934.6841: Task: Waiting for replication to finish
[1596] 090202.080434.6864: Task:            Finished waiting.
[1596] 090202.080434.6864: Setup: DsGetDcName returned: 0
[1596] 090202.080434.6864: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.080434.6864: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.080434.6864: Task:            There are 0 pending replication operations.
[1596] 090202.080434.6864: Setup:         Attempting LDAP bind.
[1596] 090202.080434.6864: Setup:         Bind successful
[1596] 090202.080434.6864: Task: Waiting for replication to finish
[1596] 090202.080934.6842: Task:            Finished waiting.
[1596] 090202.080934.6842: Setup: DsGetDcName returned: 0
[1596] 090202.080934.6842: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.080934.6842: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.080934.6842: Task:            There are 0 pending replication operations.
[1596] 090202.080934.6842: Setup:         Attempting LDAP bind.
[1596] 090202.080934.6842: Setup:         Bind successful
[1596] 090202.080934.6842: Task: Waiting for replication to finish
[1596] 090202.081434.6820: Task:            Finished waiting.
[1596] 090202.081434.6820: Setup: DsGetDcName returned: 0
[1596] 090202.081434.6820: Setup: DsGetDcName returned name: serverlrs.LRS.local
[1596] 090202.081434.6820: Setup: Expected name: SERVERLRS2.LRS.local
[1596] 090202.081434.6820: Task:            There are 0 pending replication operations.
[1596] 090202.081434.6820: Setup:         Attempting LDAP bind.
[1596] 090202.081434.6820: Setup:         Bind successful
[1596] 090202.112302.2056: Task: Replication waiting time: 08:57:27.6631902
[1596] 090202.112302.2056: Task: In Task PostDCPromoTask:
[1596] 090202.112302.2056: Setup: Task PostDCPromoTask succeeded.
[1596] 090202.112302.2056: Task: Task ("PostDCPromoTask") execution complete.
[1596] 090202.112302.3148: Task: Running Task("FixSqlGroups") with TaskProcessor("NET").
[1596] 090202.112302.3772: Task: NetLocalGroupEnum returned 0. entriesRead=39, totalEntries=39
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
SN-LRSBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:6
Avatar

--
15-02-2009 10:25  

Hei igjen og takk for god hjep hittil.

Tror kanskje at den beste løsningen for meg er pkt.5. Da sikrer jeg ihvertfall en clean SBS 2008 og samtidig vil det være tilgang til 2003 så lenge behovet er der.

 
SanderBruker er ikke pålogget
Ny bruker
Ny bruker
Send Privat Melding
Posts:1
Avatar

--
12-10-2010 09:39  
Hi!

I do apologise for not writing Norwegian, but i felt the urge to add my fix to the problem described above. I was able to fix it. and do a succesfull installation.
I noticed that the state of all the FSMO roles on both domain controllers was "ERROR". once i found this it turned out to be
a wrongly configured source domain controller. this source DC is also a DNS server, yet it had the DNS client settings pointed to the "router". Sso it coundnt resolve internal DNS names. yet the SBS Pre migration tool was installed and ran successfully.

when i entered the Primairy dns entry ( in tcp properties) to 127.0.0.1 (or it's local lan adress) it was able to query internal DNS names. Unfortunately i had to reinstall SBS again, but now it works like a charm!

take care,
Sander
Dag Staale JenssenBruker er ikke pålogget
Moderator
Moderator
Moderator
Send Privat Melding
Posts:3268
Avatar

--
12-10-2010 09:53  
Tanks for the tip!
Smallbizserver.no gjør jobben litt lettere, fordi det er det kuleste og beste it forumet i Norge!
Du er ikke autorisert til å svare.
Forums > Microsoft Small Business Server 2008 > Small Business Server 2008 Premium Server
Active Forums 4.2
Copyright 2005 by Synopus AS ARS - Powered by MS SQL and .NetNuke  smallbizserver.no  :  Betingelsene for Bruk av dette Webstedet  :  Uttalelse om Privatlivets Fred