WDS
SERVERDC – potreban je DHCP
– u c:\Deploy kopiramo datoteke, pa share na everyone
– install WDS rola
– prebacivanje na CLI2 –
– Windows deployment services konzola
na server ( desni, configure server) next, next, na kraju oznaci repsond to all…( known and unknown) i kvačica
boot image – next, lokacije bi bila C:\Deploy\winpe.wim
serverdc.racunarstvo.edu… desni,proterties – PXE response, oznaci respond i require… te staviti 3 sekunde
POWERSHELL wdsutil /Set-Server /Autoaddpolicy /Message:“Pricekajte dok administrator ne odobri boot.“
Referentni PC (CLI2) – instaliramo 7zip
– c:\Windows\System32\Sysprep\Sysprep (out-of-the-box, generalize i shutdown)
– prebacivanje na SERVERDC –
– nakon SERVERDC konfiguracije konfiguriramo na CLI2 boot preko mreže, palimo CLI2, ENTER, te approve boota na serverdc
– pokreće se CMD: net use M: \\serverdc\deploy
– dism /capture-image /imagefile:M\Win8.wim /capturedir:C:\ /Name:Win8
serverdc boot image, pa na image desni i disable
boot image, add boot image lokacije ovaj put c:\deply\boot.wim..next, next
CLI1 instalirati simx64 (Windows System Image Manager..),dodati u domenu
win system imager konzola
File -> windows image, \\serveddc\deploy\win8.wim..yes,yes..
file – new answer file
file – save answer file as i ime… \\SERVERDC\reminst\unattend
serverdc WDS, install images, add install image, u polje group WINDOWS8, next, next, next
desni na server… properties, client, enable unattend…. i pod x64 uefi odabrati datoteku unattend, ok
CLI1 izrada autom. datoteke…
windows image prošiti Components
amd64_Microsoft-Windows-international-Core-WinPE_6.3.9600
setupUIlanguage….
amd64_Microsoft-Windows-Setup_6.3.9600
DiskConfiguration
Disk
CreatePartitions
ModifyPartitions
UserData (sve)
WindowsDeploymentServices (sve)
Branchcache
serevrdc napravimo novi scope sa default gateway ( server1 ), DNS 10.10.10.1 (dc)
gpedit.msc
computer…admin temp..network..lanman server
hash publication for branchcash – enable
Hash publication actions – Allow hash publication only for sharedfolders on which BranchCache is enabled
simulacija spore brzine
Computer Configuration-> Windows Settings
create new policy, ime, npr 100 kbps
copy C:\Windows\System32\mspaint.exe C:\ShareDC
ROLA – File and Storage Services-> File and iSCSI Services
BranchCache for Network Files
server1 dodati novi mrežni adapter PMI pa start
na taj adapter staviti novi skope koji smo napravili gore na DCu (default gateway IPh) DNS 10.10.10.1 (dc)
ROLE – File and Storage Services-> File and iSCSI Services
BranchCache for Network Files
Remote Access
onda označi BranchCache next
označi routing, nexe next install
start-rras, enter
server1, configure….next, LAN routing next, finsh
start service
server1-IPv4, new routing protocol, dhcp relay agent
desni na dhcp relay agent, new interface
označi ethernet ( onaj interface sto smo dodali ), ok
desni na dhcp relay agent, properties
u polje server address 10.10.10.1 (dc), add, ok
cli1 & 2 dodati novi PMI adapter
serverdc shareDC, share, enalbe BranchCache, ok – Branchcache se uključuje na razini dijeljene mape…
server1 Branchcache poslužitelj – pa idemo kroz powershell:
Enable-BCHostedServer –RegisterSCP
Get-BCStatus
serverdc napraviti GP, edit – Computer Configuration-> Policies-> Administrative Templates-> Network-> BranchCache:
Turn on BranchCache…enable
Enable Automatic Hosted Cache Discovery by Service Connection Point…enable
Configure BranchCache for network files…enable maximum rout trip …(milisec) upisi 0, ok
CMD: netsh branchcache show status all (na cli)
Windows klaster
serverdc instaliranje iscsi role ( iscsi target, remote access(routing))
rras (lan routing…finish)
general (routing protocol, rip…)
server manager ( iscsi…task, new iscsi virtual disk)
c:, next, ime disk1, next… target NEW preko IP jednog servera i drugog)
jos jedan disk….
jos jedan disk….
server1 & 2 postaviti adrese…
iscsi initiator…
tab discovery, discover portal ( ip od dc-a, 192.168.1.1)
tab targets, oznaci i connect
server2,1 postaviti diskove (online, inicijalizacija, MBR, Simple) /refresh
server2,1 dodati rolu: File and Storage Services-> File and iSCSI Services
File server
features, failover clustering
server1 failover claster manager
validate, dodati server1 i server2, next next finish
create cluster, dodaj servere1, 2, ime, ip staviti samo 10.10.10.0/24 i staviti ip 4
kzos.racunarstvo…. storage,disk…
serevrdc dozvole/ desni klik na racunala properties, security, advanced, pa add, select principal
odabrati da trazi i racunala i naći klaster ( KZOS )
ukluči samo Create all child objects i Delete all child objects
server1 Failover claster manager – kzos.racunarstvo…. storage,disk, Add to Cluster Shared Volume
roles, configure roles, create…. File server….10.10.10.5
onda na taj napravljeni…desni i add file share, propreties, tab failover -> allow failback – Immediately
Povezivanje domena
server2 nova suma, domena….
server 1 ce biti default gateway
server1 rras – pokrenuti…
server2 napravi korisnika i stavi ka u domadmin grupu
serverdc dns, forward…new stub..algerba.edu, next next finsh
desni na algebra.edu i transfer from master
server2 dns, forward…new stub..racunarstvo.edu, next next finsh
desni na racunarstvo.edu i transfer from master (F5)
serverdc active directory domain and trusts
desni, properties, new trust, algerba.edu,
oznaci forest trust, one-way: outgoing,
both this domain and the specified. domain, selective auth., yes, confirm.. finish. Može i na properties “Validate”
AD -> uključiti advanced -> properties nekog OU -> security -> dodati usera iz druge domene