Maybe it's just my memory that's a bit faulty, but I thought that naming a workgroup was only necessary if one was planning on using the computer as part of one.
Seite 1 von 1
Why Isn't "workgroup" Optional? "User data" tab in step 3 if full unattended installation is c
Anzeige
#2
geschrieben 31. Juli 2008 - 07:07
Windows XP Setup obviously needs a name for the "WORKGROUP" from all users. That is why you automaticly become a "Client of Microsoft Network" after the installation of any Network adapter (right click onto them > "Properties").
Dieser Beitrag wurde von Fernando bearbeitet: 31. Juli 2008 - 07:08
Mein aktuelles System:
MB: ASRock Z97 Extreme6 (BIOS: 2.30)
CPU: Intel Core i5 4690
RAM: 4x4 GB G.Skill RipjawsZ DDR3-1600
System-LW: 1 TB Samsung 850 EVO SSD
Daten-LW: 2 TB Western-Digital Green HDD
Grafik: Intel HD4600
MB: ASRock Z97 Extreme6 (BIOS: 2.30)
CPU: Intel Core i5 4690
RAM: 4x4 GB G.Skill RipjawsZ DDR3-1600
System-LW: 1 TB Samsung 850 EVO SSD
Daten-LW: 2 TB Western-Digital Green HDD
Grafik: Intel HD4600
#3
geschrieben 01. August 2008 - 12:21
Zitat (Fernando: 30.07.2008, 23:07)
Windows XP Setup obviously needs a name for the "WORKGROUP" from all users. That is why you automaticly become a "Client of Microsoft Network" after the installation of any Network adapter (right click onto them > "Properties").
#4
geschrieben 01. August 2008 - 16:00
Zitat (Deof Movestofca: 01.08.2008, 13:21)
Except I'm using Windows 2000, which I believe is different (although it's entirely possible I could be wrong).
being in a workgroup OR domain is an explicit part of the microsoft network-technology. But you can only join a domain after the installation. the reason is that the domaincontroler need the "SID" of yor system. This ID will be generated after the complete installation of windows and is unique.
sorry about my bad english gramatic
#5
geschrieben 01. August 2008 - 22:41
Zitat (Stefan_der_held: 01.08.2008, 08:00)
being in a workgroup OR domain is an explicit part of the microsoft network-technology. But you can only join a domain after the installation. the reason is that the domaincontroler need the "SID" of yor system. This ID will be generated after the complete installation of windows and is unique.
Zitat (Stefan_der_held: 01.08.2008, 08:00)
sorry about my bad english gramatic
- ← Integrating Sps For Ms Apps Before Upgrading To Current Version
- english language support forum
- Xp-iso-builder Has Stuck To Creating Bootable Image. Any Help? →
Thema verteilen:
Seite 1 von 1