Skip to content

Commit

Permalink
Initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
chris18890 committed Jan 14, 2025
0 parents commit 88057e4
Show file tree
Hide file tree
Showing 5 changed files with 169 additions and 0 deletions.
17 changes: 17 additions & 0 deletions .gitattributes
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# Auto detect text files and perform LF normalization
* text=auto

# Custom for Visual Studio
*.cs diff=csharp

# Standard to msysgit
*.doc diff=astextplain
*.DOC diff=astextplain
*.docx diff=astextplain
*.DOCX diff=astextplain
*.dot diff=astextplain
*.DOT diff=astextplain
*.pdf diff=astextplain
*.PDF diff=astextplain
*.rtf diff=astextplain
*.RTF diff=astextplain
37 changes: 37 additions & 0 deletions Azure/Scripts/README.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,37 @@
Corp-Account-Management
==============

Scripts for setting up an example Network

These scripts make a couple of assumptions:

1 - you have (at least) 2 VMs:
a - one to be a "router" that has 2 nework interfaces, 1 public and 1 private.
Make sure that the interface names are set correctly in \Scripts\machine1\Setup-Router.ps1
b - one to be a DC/file server
2 - you copy the \scripts folder to C:\Scripts on each machine
3 - when running the setup scripts the -Domain param is the NetBIOS name of the domain
only, and the -DomainSuffix param is the external domain. EG if you supply -Domain
"Corp" and -DomainSuffix "company.com" your AD domain will be called "corp.company.com".
Ideally make the -EmailSuffix the same as -DomainSuffix to give your users a sensible
email address and UPN values, EG <username>@company.com for the UPN and
[email protected] for the email address
Users can be added by modifying the \Scripts\Users\Users.CSV file

To Run -
1 - Copy the folder to C:\Scripts on each machine
2 - on the DC, run \Scripts\Machine1\setup.ps1 and enter a NetBIOS domain name
then run \Scripts\Machine1\dcpromo.ps1 and enter a NetBIOS domain name and Domain Suffix
when prompted
3 - Once the DC has been set up on the DC, run \Scripts\Prelim\DomainSetup.ps1 and enter
an email suffix, CD to \Scripts\Users and run CreateUsers.ps1, choose N for office365
and enter the same email suffix as before, and a password when prompted
4 - on the router VM, open \Scripts\Machine1\setup-router.ps1 in notepad to check that the
network interfaces are set
5 - on the router VM, run \Scripts\Machine1\setup-router.ps1 and enter a NetBIOS domain name
6 - on the router VM, run \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name,
enter the domain admin credentials in the pop up to add the machine to the domain
7 - on the router VM, rerun \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name
8 - download the contents of
https://www.dropbox.com/sh/n76ntsil0zjaapn/AAAEp7KrtLvLZk9_EFaExJIza?dl=0
and put it in \\<Domain>\Share\Software
21 changes: 21 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2021 Chris Murray

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
53 changes: 53 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
Corp-Account-Management
==============

Scripts for setting up an example Network

These scripts make a couple of assumptions:

1 - you have (at least) 2 VMs running fresh installs of Windows Server, at least 2022, with C: and D: drives:

a - one to be a "router" that has 2 nework interfaces, 1 public and 1 private.
Make sure that the interface names are set correctly in \Scripts\machine1\Setup-Router.ps1

b - one to be a DC/file server

2 - you copy the \scripts folder to C:\Scripts on each machine

3 - when running the setup scripts the -Domain param is the NetBIOS name of the domain only, and the
-DomainSuffix param is the external domain. EG if you supply -Domain "Corp" and -DomainSuffix
"company.com" your AD domain will be called "corp.company.com". Ideally make the -EmailSuffix
the same as -DomainSuffix to give your users a sensible email address and UPN values, EG
[email protected] for the UPN and [email protected] for the email address.
Users can be added by modifying the \Scripts\Users\Users.CSV file.

To Run:

1 - Copy the folder to C:\Scripts on each machine

2 - on the DC, run \Scripts\Machine1\setup.ps1 and enter a NetBIOS domain name then run
\Scripts\Machine1\dcpromo.ps1, enter a NetBIOS domain name and Domain Suffix when
prompted

3 - Once the DC has been set up, on the DC run \Scripts\Prelim\DomainSetup.ps1 and enter
an email suffix, CD to \Scripts\Users and run CreateUsers.ps1, choose N for office365
and enter the same email suffix as before, and a password when prompted

4 - on the router VM, open \Scripts\Machine1\setup-router.ps1 in notepad to check that the
network interfaces are set

5 - on the router VM, run \Scripts\Machine1\setup-router.ps1 and enter a NetBIOS domain name

6 - on the router VM, run \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name,
enter the domain admin credentials in the pop up to add the machine to the domain

7 - on the router VM, rerun \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name

8 - download the contents of
https://www.dropbox.com/sh/n76ntsil0zjaapn/AAAEp7KrtLvLZk9_EFaExJIza?dl=0
and put it in \\Domain\Share\Software

9 - Optional - on the router VM run \Scripts\WDS\wds.ps1, then mount ISOs for Server
2022 and Win10, and run the corresponding .PS1 script to set up the install
images. You can now create additional VMs that will do network installs. Machines
need to have a private network adaptor.
41 changes: 41 additions & 0 deletions Scripts/README.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
Corp-Account-Management
==============

Scripts for setting up an example Network

These scripts make a couple of assumptions:

1 - you have (at least) 2 VMs:
a - one to be a "router" that has 2 nework interfaces, 1 public and 1 private.
Make sure that the interface names are set correctly in \Scripts\machine1\Setup-Router.ps1
b - one to be a DC/file server
2 - you copy the \scripts folder to C:\Scripts on each machine
3 - when running the setup scripts the -Domain param is the NetBIOS name of the domain
only, and the -DomainSuffix param is the external domain. EG if you supply -Domain
"Corp" and -DomainSuffix "company.com" your AD domain will be called "corp.company.com".
Ideally make the -EmailSuffix the same as -DomainSuffix to give your users a sensible
email address and UPN values, EG <username>@company.com for the UPN and
[email protected] for the email address
Users can be added by modifying the \Scripts\Users\Users.CSV file

To Run -
1 - Copy the folder to C:\Scripts on each machine
2 - on the DC, run \Scripts\Machine1\setup.ps1 and enter a NetBIOS domain name
then run \Scripts\Machine1\dcpromo.ps1 and enter a NetBIOS domain name and Domain Suffix
when prompted
3 - Once the DC has been set up on the DC, run \Scripts\Prelim\DomainSetup.ps1 and enter
an email suffix, CD to \Scripts\Users and run CreateUsers.ps1, choose N for office365
and enter the same email suffix as before, and a password when prompted
4 - on the router VM, open \Scripts\Machine1\setup-router.ps1 in notepad to check that the
network interfaces are set
5 - on the router VM, run \Scripts\Machine1\setup-router.ps1 and enter a NetBIOS domain name
6 - on the router VM, run \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name,
enter the domain admin credentials in the pop up to add the machine to the domain
7 - on the router VM, rerun \Scripts\Machine1\dhcp.ps1 and enter a NetBIOS domain name
8 - download the contents of
https://www.dropbox.com/sh/n76ntsil0zjaapn/AAAEp7KrtLvLZk9_EFaExJIza?dl=0
and put it in \\<Domain>\Share\Software
9 - Optional - on the router VM run \Scripts\WDS\wds.ps1, then mount ISOs for Server
2019 and Win10, and run the corresponding .PS1 script to set up the install
images. You can now create additional VMs that will do network installs. Machines
need to have a private network adaptor.

0 comments on commit 88057e4

Please sign in to comment.