Avatar billede densortehingst Seniormester
10. oktober 2003 - 09:05 Der er 11 kommentarer og
1 løsning

Kopiering af operativsystem til ny maskine.

Hej.
Jeg har en maskine der er installeret med win xp pro og diverse programmer. Jeg vil gerne flyttet hele indholdet af disken til en ny maskine, så de er 100 % ens. Jeg har forsøgt med norton ghost og deploy center. Jeg kan godt lave og kopiere mit image, men maskinen vil ikke starte op på det image jeg lægger på.
Jeg har ingen problemer, når jeg flytter mellem 2 ens maskiner, men når jeg flytter mellem 2 forskellige typer maskiner, så går det galt. Det fungerede fint i windows98, hvor den selv gik ud og fandt alt den hardware der var forskellig, men ikke under xp. Jeg tror, at det kan lade sig gøre, men hvordan ????
Jeg står med 350 forskellige maskiner, hvor jeg skal lægge det samme image på alle, derfor de høje point.
På forhånd tak.
Avatar billede zybug Nybegynder
10. oktober 2003 - 09:09 #1
Siger du ikke at Xp maskinerne er 100% ens ?
Avatar billede ironmaiden Nybegynder
10. oktober 2003 - 09:10 #2
det kommer an på hvilken version du har af ghost... den skal jo også være så opdateret at den kan køre med XP.. kører selv med 2003 versionen af ghost og det virker fint med xp
Avatar billede zybug Nybegynder
10. oktober 2003 - 09:13 #3
Jeg mener altså heller ikke der er nogle problemer med Ghost og Xp maskiner !
Avatar billede dinkie Nybegynder
10. oktober 2003 - 09:18 #4
Du får nok svært ved blot at ghoste dem - da der kan være stor forskel på hvilken controller type der styrer dine diske. Hvis den driver ikke er den rigtige kommer den ikke lige op at køre igen uden videre.

Men det du kan overveje er at bruge sysprep. Godt nok er der mere arbejde i det - men noget at det kan du scripte dig ud af eller lave et unattended setup til det sysprepede image.
Avatar billede peet-49 Novice
10. oktober 2003 - 09:19 #5
Hvis du ghoster til en maskine, der ikke har samme hardware, skal der køres en repair af XP
Avatar billede rarom Nybegynder
10. oktober 2003 - 09:42 #6
så vidt jeg husker kan du løbe ind i problemer hvis du installere dine pc'er via et ghost image. Det har noget at gøre med SID på maskinen er så vil være ens. Ret mig hvis jeg ikke har ret!.

Det jeg ville gøre hvis du har ën Windows 2000/2003 server er at installere RIS og rulle maskinerne ud med den. Det gør også at du kan sætte flere maskiner igang på samme tid. Hvad der skal være af applikationer på maskinen kan du også klare via RIS eller GPOer i AD. Det kan være et stort arbejde men når det først er gjort vil du meget nemmere kunne administrere dine pc'er og tilføje nye typer og hardware. jeg har vedlagt et link til en beskrivelse af hvordan du griber sagen an.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windows2000serv/deploy/depopt/remosad.asp

håber det kan hjælpe dig.
Avatar billede rarom Nybegynder
10. oktober 2003 - 09:46 #7
undskyld ikke SID med GUID
Avatar billede webhest Nybegynder
10. oktober 2003 - 11:04 #8
Umiddelbart ville jeg mene at du IKKE kan kopire dit windows som du har lige nu, og så bagefter ligge på dit c drev igen!
Jeg vil mene at du skal installere WindowsXP fra nu!
De gange jeg har prøvet på det, mangler den nogle ting i registrationsdatabasen!
Så jeg mener ikke at du bare kan gøre det!
Avatar billede hcma Novice
10. oktober 2003 - 11:13 #9
såfremt hardware-konfigurationen ikke er den samme på maskinerne, kan du ikke Ghoste, da det vil give bl.a. driverproblemer.
Avatar billede reklamefridk Nybegynder
10. oktober 2003 - 11:24 #10
Den finder i hvert fald ingen ændret hardware hvis den ikke vil starte op..
Hvor langt kommer den i opstarten?
Er det forskelligt fra maskine til maskine?
Hvor forskellige slags maskiner er der tale om?
Avatar billede densortehingst Seniormester
04. november 2003 - 15:59 #11
det enkle svar på opgave er følgende, som jeg håber andre måske kan have glæde af. Svaret fandt jeg på en eller anden Microsoft side og det virker faktisk !!!

Produkter  |  Support  |  Søg  |  Microsoft websteder

--------------------------------------------------------------------------------
Office
Windows
Serversoftware
Hardware
Spil
Produkter til Macintosh
Litteratur fra Microsoft

--------------------------------------------------------------------------------
Produktkatalog
Forhandlere
Licensinformation

--------------------------------------------------------------------------------
Microsoft Danmark
MSN.dk

--------------------------------------------------------------------------------
Microsoft Corp
Microsoft Worldwide

--------------------------------------------------------------------------------
Oversigt over webstedet
Min profil
Integritet og sikkerhed
  Startside      Windows      Office      Spil og hardware      Tekniske supportartikler (KB)      Sikkerhed      Hent filer      Kontaktinformation   

Knowledge Base-artikel - 314082   

Kommentarer?
Giv feedback på denne artikel

Produktspecifik support
Windows XP 

Generelle oplysninger
Kontakt Microsoft Support
Oplysninger om Microsofts supportaftaler, telefonnummer og øvrige supportalternativer

Microsoft Salgssupport
Microsoft Salgssupport hjælper dig med oplysninger om Microsofts produkter, licenser, arrangementer, certificeringer m.m.


Sideindstillinger
Send til en ven
Udskriv


You Receive a Stop 0x0000007B Error After You Move the Windows XP System Disk to Another Computer
Gælder for
This article was previously published under Q314082
SYMPTOMS
After you move the system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows-based backup computer:

STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE
CAUSE
This error can occur if the registry entries and drivers for the mass storage controller hardware in the backup computer are not installed in Windows.

For integrated device electronics (IDE) controllers, there are several different chip sets available, such as Intel, VIA, and Promise. Each chip set has a different Plug-n-Play identifier (PnP-ID).

The PnP-ID information of mass storage controllers for the backup computer must be in the registry before startup so that Windows can initialize the correct drivers.
RESOLUTION
To resolve this error, follow these steps for system recovery:
Use identical hardware for the backup computer.
Replace the problem hardware components in the backup computer with components of the same manufacturer, make, and model as the components in the computer that you are backing up.
If the system disk is a SCSI disk, use the same make and model of SCSI controller in the new computer.
If the system disk is an IDE disk, use the same kind of motherboard in the new computer, a motherboard that has the same kind of IDE chip set and the same PnP-ID as the motherboard in the computer that you are backing up.
For SCSI-based system disks, you can prime the registry and ensure that the drivers that you want are in place by installing the SCSI controller that is used by the backup computer before you transfer the system disk contents. Windows PnP detects the controller, sets up critical registry entries, and copies the appropriate driver.

After you see the SCSI controller in Device Manager, you can safely remove the alternate controller. If, at a later time, you need to move the system disk to another computer that has the same make and model of SCSI controller, Windows will start successfully because Windows has already used that controller once and has retained the correct configuration information.
MORE INFORMATION
Although Microsoft does not support this method, it is possible to import or merge the required registry entries, and to copy the drivers ahead of time to support all IDE controllers that are natively supported by Windows. Note that although this method might enable the relocated system disk to start successfully, other hardware differences may lead to other problems.

This solution provides support for IDE controllers whose PnP-ID matches one of the PnP-IDs in the following list. However, if you want to determine ahead of time which IDE controllers are used in your current and backup computers, you can search the %SystemRoot%\Setupapi.log file for the PnP-ID that is detected during Setup.

After you determine which PnP-IDs are used in your computers, you can choose to merge or to populate the registry with only the PnP-IDs that you need.

The following list shows the PnP-IDs of natively supported IDE controllers in Windows.    ;*********** Standard IDE ATA/ATAPI Controllers *********
  Secondary_IDE_Channel=%SystemRoot%\inf\Mshdc.inf

  ;*********** Generic ESDI Hard Disk_Controller **********
  *PNP0600=%SystemRoot%\inf\Mshdc.inf

  ;*********** Aztech IDE Controller **********************
  *AZT0502=%SystemRoot%\inf\Mshdc.inf

  ;*********** Device ID for Generic Dual PCI IDE *********
  PCI\CC_0101=%SystemRoot%\inf\Mshdc.inf

  ;************ALI IDE Controller ******************************
  PCI\VEN_10B9&DEV_5215=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_10B9&DEV_5219=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_10B9&DEV_5229=%SystemRoot%\inf\Mshdc.inf

  ;************Appian Technology **************************
  PCI\VEN_1097&DEV_0038=%SystemRoot%\inf\Mshdc.inf

  ;************CMD Technology *****************************
  PCI\VEN_1095&DEV_0640=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1095&DEV_0646=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1095&DEV_0646&REV_05=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1095&DEV_0646&REV_07=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1095&DEV_0648=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1095&DEV_0649=%SystemRoot%\inf\Mshdc.inf

  ;************Compaq *************************************
  PCI\VEN_0E11&DEV_AE33=%SystemRoot%\inf\Mshdc.inf

  ;*************Intel *************************************
  PCI\VEN_8086&DEV_1222=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_1230=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_7010=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_7111=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_2411=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_2421=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_7199=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_244A=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_244B=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_248A=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_7199=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_8086&DEV_7601=%SystemRoot%\inf\Mshdc.inf

  ;*************PC Technology *****************************
  PCI\VEN_1042&DEV_1000=%systemroot%\inf\Mshdc.inf

  ;*************Silicon Integrated System *****************
  PCI\VEN_1039&DEV_0601=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_1039&DEV_5513=%SystemRoot%\inf\Mshdc.inf

  ;*************Symphony Labs *****************************
  PCI\VEN_10AD&DEV_0001=%SystemRoot%\inf\Mshdc.inf
  PCI\VEN_10AD&DEV_0150=%SystemRoot%\inf\Mshdc.inf

  ;*************Promise Technology ************************
  PCI\VEN_105A&DEV_4D33=%SystemRoot%\inf\mshdc.inf

  ;*************VIA Technologies, Inc. ********************
  PCI\VEN_1106&DEV_0571=%SystemRoot%\inf\Mshdc.inf

  ;*************Standard Microsystems Corp. ***************
  PCI\VEN_1055&DEV_9130=%SystemRoot%\inf\Mshdc.inf

  ;*************Toshiba ***********************************
  PCI\VEN_1179&DEV_0105=%SystemRoot%\inf\Mshdc.inf

               
To import this information, use the following procedure on two different test computers that exhibit the Stop 0x0000007B error after you change disks between computers. After you follow this procedure on each test computer, you can probably move the hard disks and start both computers without receiving the Stop 0x0000007B error. However, other hardware differences might result in other problems.
Copy the following information into Notepad, and then save the file on a 3.5-inch disk. Name the file Mergeide.reg, without the .txt file name extension. ********** Start copy here **********
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase \pci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires Atapi.sys in Drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
  00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\
  00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers directory)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
  00,2e,00,73,00,79,00,73,00,00,00
                   
********** End copy here **********


Extract the Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys files from the %SystemRoot%\Driver Cache\I386\Driver.cab file, or copy the files to the %SystemRoot%\System32\Drivers folder.
In Windows Explorer, right-click the Mergeide.reg file in the floppy drive, and then click Merge. Windows displays the following message:
Are you sure you want to add the information in A:\Mergeide.reg to the registry?

Click Yes.

After the import process is completed, Windows displays another message:
Information from A:\Mergeide.reg was successfully entered into the registry.

Shut down Windows, turn off the computer, and then move the system disk to the other test computer, the one that previously produced a Stop 0x0000007B error, and then see whether you can successfully start the second computer.
The information in this article applies to:
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional
Last Reviewed: 4/24/2003 (2.1) 
Keywords: kb3rdparty kbenv kbprb KB314082





Send til en ven  Udskriv  Hjælp 


© 2003 Microsoft Corporation. Alle rettigheder forbeholdes. Juridisk meddelelse.  Integritet og sikkerhed  Hjælp til handicappede
Avatar billede peet-49 Novice
04. november 2003 - 17:04 #12
Det var dog en langsommelig vej for, at ghoste en HD, når jeg ghoster med 2003 tager det hele et par minutter.
Avatar billede Ny bruger Nybegynder

Din løsning...

Tilladte BB-code-tags: [b]fed[/b] [i]kursiv[/i] [u]understreget[/u] Web- og emailadresser omdannes automatisk til links. Der sættes "nofollow" på alle links.

Loading billede Opret Preview
Kategori
IT-kurser om Microsoft 365, sikkerhed, personlig vækst, udvikling, digital markedsføring, grafisk design, SAP og forretningsanalyse.

Log ind eller opret profil

Hov!

For at kunne deltage på Computerworld Eksperten skal du være logget ind.

Det er heldigvis nemt at oprette en bruger: Det tager to minutter og du kan vælge at bruge enten e-mail, Facebook eller Google som login.

Du kan også logge ind via nedenstående tjenester