You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/en-us/c4b-environments/quick-start-environment/chocolatey-for-business-quick-start-guide.mdx
+29-46Lines changed: 29 additions & 46 deletions
Original file line number
Diff line number
Diff line change
@@ -100,8 +100,7 @@ export const callout3 = {
100
100
- Run the following to zip up your offline bundle: `Compress-Archive -Path ~\Downloads\choco-quickstart-scripts\choco-quickstart-scripts-main\* -DestinationPath ~\Downloads\C4B-Files.zip`.
101
101
- Transfer the `C4B-Files.zip` from your downloads folder to your offline system. All further steps will be carried out on the offline system.
102
102
- Run `Expand-Archive -Path \path\to\C4B-Files.zip -DestinationPath C:\choco-setup\files -Force` on your offline system.
103
-
- Run `Set-Location "$env:SystemDrive\choco-setup\files"; Set-ExecutionPolicy Bypass Process; .\Start-C4bSetup.ps1` on your offline system.
> <summary><strong>What does this script do? (click to expand)</strong></summary>
130
-
> <ulclass="list-style-type-disc">
131
-
> <li>Installs Chocolatey client from https://community.chocolatey.org</li>
132
-
> <li>Prompts for your C4B license file location, with validation</li>
133
-
> <li>Converts your C4B license into a Chocolatey package</li>
134
-
> <li>Configures local "choco-setup" directories</li>
135
-
> <li>Downloads setup files from "choco-quickstart-scripts" GitHub repo</li>
136
-
> <li>Downloads Chocolatey packages required for setup</li>
137
-
> </ul>
138
-
> </details>
125
+
#### Certificate Options
139
126
140
-
<Calloutcontent={callout3}>
141
-
You can now copy the `C:\choco-setup\` directory to any computer to continue the installation. To zip up that directory, run `Compress-Archive -Path C:\choco-setup\files\* -DestinationPath C:\choco-setup\C4B-Files.zip`. Move the archive to your new machine, and run `Expand-Archive -Path /path/to/C4B-Files.zip -DestinationPath C:\choco-setup\files -Force`. You should then run `Set-Location "$env:SystemDrive\choco-setup\files"; .\Start-C4bSetup.ps1`, and continue with the guide.
142
-
</Callout>
127
+
**Custom SSL Certificate** - If you have your own custom SSL certificate (purchased/acquired, or from your Domain CA), you can paste and run the following script with the `Thumbprint` value of your SSL certificate specified:
**ALTERNATIVE 1 : Custom SSL Certificate** - If you have your own custom SSL certificate (purchased/acquired, or from your Domain CA), you can paste and run the following script with the `Thumbprint` value of your SSL certificate specified:
141
+
For example, with a wildcard certificate with a thumbprint of `deee9b2fabb24bdaae71d82286e08de1`you wish to use `chocolatey.foo.org`, the following would be required:
A Role and User credential will be configured to limit access to your Nexus repositories. As well, CCM Client and Service Salts are configured to further encrypt your connection between CCM and your endpoint clients. These additional settings are also incorporated into your `Register-C4bEndpoint.ps1` script for onboarding endpoints.
159
154
</Callout>
160
155
161
-
**ALTERNATIVE 2 : Wildcard SSL Certificate** - If you have a wildcard certificate, you will also need to provide a DNS name you wish to use for that certificate:
156
+
**Self-Signed Certificate** - If you are running a bare-minimum proof of concept environment, you can generate a self-signed certificate and use that.
For example, with a wildcard certificate with a thumbprint of `deee9b2fabb24bdaae71d82286e08de1` you wish to use `chocolatey.foo.org`, the following would be required:
> <summary><strong>What does this script do? (click to expand)</strong></summary>
165
+
> <ulclass="list-style-type-disc">
166
+
> <li>Installs Chocolatey client from https://community.chocolatey.org</li>
167
+
> <li>Prompts for your C4B license file location, with validation</li>
168
+
> <li>Converts your C4B license into a Chocolatey package</li>
169
+
> <li>Configures local "choco-setup" directories</li>
170
+
> <li>Downloads setup files from "choco-quickstart-scripts" GitHub repo</li>
171
+
> <li>Downloads Chocolatey packages required for setup</li>
172
+
> </ul>
173
+
> </details>
174
174
175
175
#### Script: Nexus Setup
176
176
@@ -236,23 +236,6 @@ As part of the C4B setup, we create a readme and install the Chocolatey Agent on
236
236
A `Readme.html` file will now be generated on your desktop. This file contains login information for all 3 web portals (CCM, Nexus, and Jenkins). This `Readme.html`, along with all 3 web portals, will automatically be opened in your browser.
237
237
</Callout>
238
238
239
-
#### Script: Verification
240
-
241
-
As a part of the C4B setup, we run tests to validate that your environment is correctly configured:
242
-
243
-
> <details>
244
-
> <summary><strong>What does this script do? (click to expand)</strong></summary>
245
-
> <ulclass="list-style-type-disc">
246
-
> <li>Verifies Nexus Repository installation</li>
247
-
> <li>Verifies Central Management installation</li>
248
-
> <li>Verifies Jenkins installation</li>
249
-
> <li>Ensures system firewall is configured</li>
250
-
> <li>Ensures Windows Features are installed</li>
251
-
> <li>Ensures services are correctly configured</li>
252
-
> <li>Ensured README is created</li>
253
-
> </ul>
254
-
> </details>
255
-
256
239
### Step 2: Setting up Endpoints
257
240
258
241
1. Find the `Register-C4bEndpoint.ps1` script in the `C:\choco-setup\files\scripts\` directory on your C4B Server. Copy this script to your client endpoint.
0 commit comments