From d76d33744a039dc3e9252f89836c1343a06d8da0 Mon Sep 17 00:00:00 2001 From: Rachael Shaw Date: Tue, 14 Jan 2025 12:03:45 -0600 Subject: [PATCH] #25108: Update casing after step numbers (#25418) + Capitalize the 1st word of phrases that come after step numbers + Various other sentence-case fixes I noticed while I was in there --- articles/alternate-apple-mdm-url.md | 12 ++++++------ articles/battery-health.md | 2 +- ...kta-verify-on-macOS-with-configuration-profile.md | 2 +- articles/how-to-configure-logging-destinations.md | 2 +- articles/macos-setup-experience.md | 12 ++++++------ articles/mdm-migration.md | 6 +++--- articles/puppet-module.md | 6 +++--- articles/software-self-service.md | 2 +- ...-from-fleet-security-securing-google-workspace.md | 8 ++++---- articles/windows-mdm-setup.md | 8 ++++---- 10 files changed, 30 insertions(+), 30 deletions(-) diff --git a/articles/alternate-apple-mdm-url.md b/articles/alternate-apple-mdm-url.md index 6cda5188c8..8165176372 100644 --- a/articles/alternate-apple-mdm-url.md +++ b/articles/alternate-apple-mdm-url.md @@ -1,4 +1,4 @@ -# Configuring an Alternative Apple MDM URL +# Configuring an alternative Apple MDM URL Fleet [v4.59.0](https://github.com/fleetdm/fleet/releases/tag/fleet-v4.59.0) allows setting an alternative MDM URL helps organizations differentiate MDM traffic from other Fleet traffic, allowing the application of network rules specific to MDM communications. The `mdm.apple_server_url` configuration specifies the URL that Apple devices use to communicate with your Fleet instance for MDM purposes. This configuration is optional; if not set, MDM will default to using the Fleet Server URL. @@ -8,9 +8,9 @@ However, be aware that changing this URL after devices have been enrolled in MDM * Fleet v4.59.0 -## Step-by-Step Instructions +## Step-by-step instructions -1. Prepare Your DNS +1. Prepare your DNS Create a DNS record Fleet can use for Apple MDM traffic @@ -20,13 +20,13 @@ However, be aware that changing this URL after devices have been enrolled in MDM Both URLs should point to the same IP address to ensure seamless handling of both MDM and non-MDM traffic. -2. Configure the Apple Server URL in Fleet +2. Configure the Apple server URL in Fleet Via the Fleet UI: - * **Access Fleet UI**: Navigate to **Settings > Organization settings > Apple Server URL**. + * **Access Fleet UI**: Navigate to **Settings > Organization settings > Advanced options > Apple server URL**. * **Set the URL**: Enter your MDM Apple Server URL. - * **Apply Changes**: Run the following command to apply your changes: + * **Apply changes**: Run the following command to apply your changes: Via GitOps: diff --git a/articles/battery-health.md b/articles/battery-health.md index 485bfd3b9c..77a5cf77b9 100644 --- a/articles/battery-health.md +++ b/articles/battery-health.md @@ -11,7 +11,7 @@ In today's mobile-driven workplace, the health of a device's battery plays a cru - osquery v.5.12.0+ on Windows - osquery v3.2.7+ on macOS -## Step-by-Step Instructions +## Step-by-step instructions ### Accessing battery health diff --git a/articles/enable-okta-verify-on-macOS-with-configuration-profile.md b/articles/enable-okta-verify-on-macOS-with-configuration-profile.md index 15dc2ecfbf..5a7a59b1f3 100644 --- a/articles/enable-okta-verify-on-macOS-with-configuration-profile.md +++ b/articles/enable-okta-verify-on-macOS-with-configuration-profile.md @@ -10,7 +10,7 @@ By following these steps, you can automate the deployment of Okta Verify across * MDM enabled and configured -## Step-by-Step Instructions +## Step-by-step instructions ### **Step 1: Install Okta Verify on your hosts** diff --git a/articles/how-to-configure-logging-destinations.md b/articles/how-to-configure-logging-destinations.md index cf6ea57c28..a64b6b437c 100644 --- a/articles/how-to-configure-logging-destinations.md +++ b/articles/how-to-configure-logging-destinations.md @@ -62,7 +62,7 @@ Before streaming data, ensure that you have the necessary infrastructure. The re - Region -### Step 2: configure your destination +### Step 2: Configure your destination #### For Sumo Logic diff --git a/articles/macos-setup-experience.md b/articles/macos-setup-experience.md index 0e287879cb..59d6b8fd55 100644 --- a/articles/macos-setup-experience.md +++ b/articles/macos-setup-experience.md @@ -60,7 +60,7 @@ To add a bootstrap package to Fleet, we will do the following steps: 3. Upload the package to Fleet 4. Confirm package is uploaded -### Step 1: download or generate a package +### Step 1: Download or generate a package Whether you have to download or generate a package depends on what you want to deploy using your bootstrap package: @@ -87,7 +87,7 @@ Apple requires that your package is a distribution package. Verify that the pack Make sure your package is a `.pkg` file. -### Step 2: sign the package +### Step 2: Sign the package To sign the package we need a valid Developer ID Installer certificate: @@ -114,7 +114,7 @@ To sign the package we need a valid Developer ID Installer certificate: In the output you should see that your package has a "signed" status. -### Step 3: upload the package to Fleet +### Step 3: Upload the package to Fleet 1. Head to the **Controls > Setup experience > Bootstrap package** page. @@ -134,7 +134,7 @@ To customize the macOS Setup Assistant, we will do the following steps: 2. Upload the profile to Fleet 3. Test the custom macOS Setup Assistant -### Step 1: create an automatic enrollment profile +### Step 1: Create an automatic enrollment profile 1. Download Fleet's example automatic enrollment profile by navigating to the example [here](https://fleetdm.com/example-dep-profile) and clicking the download icon. @@ -146,7 +146,7 @@ To customize the macOS Setup Assistant, we will do the following steps: > You can modify properties other than `skip_setup_items`. These are documented by Apple [here](https://developer.apple.com/documentation/devicemanagement/profile). -### Step 2: upload the profile to Fleet +### Step 2: Upload the profile to Fleet 1. Head to the **Controls > Setup experience > Setup assistant** page. @@ -154,7 +154,7 @@ To customize the macOS Setup Assistant, we will do the following steps: 3. Select **Add profile** and choose your profile package. -### Step 3: test the custom macOS Setup Assistant +### Step 3: Test the custom macOS Setup Assistant Testing requires a test Mac that is present in your Apple Business Manager (ABM) account. We will wipe this Mac and use it to test the custom macOS Setup Assistant. diff --git a/articles/mdm-migration.md b/articles/mdm-migration.md index 5ffbfc0e9e..1c23847574 100644 --- a/articles/mdm-migration.md +++ b/articles/mdm-migration.md @@ -18,18 +18,18 @@ To migrate hosts, we will do the following steps: 2. Assign hosts in Apple Business Manager (ABM) to Fleet 3. Choose migration workflow and migrate hosts -### Step 1: enroll hosts to Fleet +### Step 1: Enroll hosts to Fleet 1. First, enroll your hosts to Fleet by installing Fleet's agent (fleetd). Learn how [here](https://fleetdm.com/guides/enroll-hosts). 2. Ensure your end users have access to an admin account on their Mac. End users won't be able to migrate on their own if they have a standard account. -### Step 2: assign hosts in Apple Business Manager (ABM) to Fleet +### Step 2: Assign hosts in Apple Business Manager (ABM) to Fleet 1. In ABM, unassign your hosts from your current MDM solution by selecting **Devices** and then selecting **All Devices**. Then, select **Edit** next to **Edit MDM Server**, select **Unassign from the current MDM**, and select **Continue**. 2. Assign these hosts to Fleet: select **Devices** and then select **All Devices**. Then, select **Edit** next to **Edit MDM Server**, select **Assign to the following MDM:**, select your Fleet server in the dropdown, and select **Continue**. -### Step 3: choose migration workflow and migrate hosts +### Step 3: Choose migration workflow and migrate hosts There are two migration workflows in Fleet: default and end user. diff --git a/articles/puppet-module.md b/articles/puppet-module.md index c0c3e9e946..740ba55e8b 100644 --- a/articles/puppet-module.md +++ b/articles/puppet-module.md @@ -14,11 +14,11 @@ To set up the Puppet module, we will do the following steps: 2. Configure Puppet to talk to Fleet using Hiera 3. Set Fleet as a reporter -### Step 1: install the Puppet module +### Step 1: Install the Puppet module Install [Fleet's Puppet module](https://forge.puppet.com/modules/fleetdm/fleetdm/readme). For more instructions on how to install Puppet modules, check out the Puppet docs [here](https://www.puppet.com/docs/puppet/8/modules_installing.html). -### Step 2: configure Puppet to talk to Fleet using Heira +### Step 2: Configure Puppet to talk to Fleet using Heira 1. In Fleet, create an API-only user with the GitOps role. Instructions for creating an API-only user are [here](https://fleetdm.com/guides/fleetctl#create-api-only-user). @@ -35,7 +35,7 @@ Puppet docs on configuring Hiera are [here](https://www.puppet.com/docs/puppet/6 If you have staging and production Puppet environments, you can optionally set different values for each environment. This allows you to have your staging and production environments that talk to separate staging and production Fleet servers. -### Step 3: set Fleet as a reporter +### Step 3: Set Fleet as a reporter In your Puppet configuration, set `http:fleetdm` as the value for `reports`. Here's an example of the Puppet configuration: diff --git a/articles/software-self-service.md b/articles/software-self-service.md index 07ad2502a1..1f3e2be850 100644 --- a/articles/software-self-service.md +++ b/articles/software-self-service.md @@ -10,7 +10,7 @@ Fleet’s self-service software feature empowers end users by allowing them to i > Software packages can be added to a specific team or to the "No team" category. The "No team" category is the default assignment for hosts that are not part of any specific team. -## Step-by-Step Instructions +## Step-by-step instructions ### Adding a self-service software package diff --git a/articles/tales-from-fleet-security-securing-google-workspace.md b/articles/tales-from-fleet-security-securing-google-workspace.md index 5f8e4db367..b9cc849c7b 100644 --- a/articles/tales-from-fleet-security-securing-google-workspace.md +++ b/articles/tales-from-fleet-security-securing-google-workspace.md @@ -1,4 +1,4 @@ -# Tales from Fleet security: securing Google Workspace +# Tales from Fleet security: Securing Google Workspace ![Securing Google Workspace](../website/assets/images/articles/tales-from-fleet-security-securing-google-workspace-cover-1600x900@2x.jpg) @@ -27,9 +27,9 @@ Configuring Google Workspace is straightforward, but we did encounter a few chal 3. Retroactively controlling third-party apps with access to Google Workspace can be challenging, as many workflows are already in place and many apps already have access to data. 4. Third-party email clients do not have good security UX compared to Gmail, which adds handy messages on top of suspicious messages. -## Overcoming Those Challenges +## Overcoming those challenges -### 2FA/MFA/Two-Step Verification +### 2FA/MFA/Two-step verification We started by disabling the most unsafe methods (SMS and voice) and promoting the use of hardware security keys and [phones and tablets](https://support.google.com/accounts/answer/9289445?hl=en&co=GENIE.Platform%3DAndroid) as hardware security keys for access to Google. By the end of next week, all privileged access at Fleet will require hardware security keys, thanks to Yubico shipping to an extensive list of countries, making this easy to achieve in an international remote company. @@ -39,7 +39,7 @@ To support MDM enrollment, we limit the generation of codes to the user’s loca >Note: GitHub supports using your Mac with Touch ID as a key in Chrome. That is awesome. -### SSO and Lack of SSO +### SSO and lack of SSO Where it makes sense, we will upgrade to the tier needed to get proper SSO from other SaaS vendors. The extra spending is an annoyance, but having to disable 17 accounts manually every time someone leaves the company and worrying about password re-use and 2FA settings on all the same applications is not worth it. diff --git a/articles/windows-mdm-setup.md b/articles/windows-mdm-setup.md index 5937657012..e2b0ad2c28 100644 --- a/articles/windows-mdm-setup.md +++ b/articles/windows-mdm-setup.md @@ -147,17 +147,17 @@ Testing automatic enrollment requires creating a test user in Microsoft Entra ID Fleet can automatically migrate your Windows hosts from another MDM solution to Fleet without end user interaction. -### Step 1: set up Windows MDM in Fleet +### Step 1: Set up Windows MDM in Fleet Follow the [steps above](#manual-enrollment) to turn on Windows MDM in Fleet. -### Step 2: install Fleet's agent on the hosts +### Step 2: Install Fleet's agent on the hosts 1. [Enroll](https://fleetdm.com/docs/using-fleet/enroll-hosts) the Windows hosts you want to migrate to Fleet. 2. Navigate to the **Hosts** tab in the main navigation bar and wait until your hosts are visible in the hosts list. -### Step 3: enable automatic migration +### Step 3: Enable automatic migration 1. Head back to the **Settings > Integrations > Mobile device management (MDM)** page. @@ -165,7 +165,7 @@ Follow the [steps above](#manual-enrollment) to turn on Windows MDM in Fleet. 3. On the **Manage Windows MDM** page, select **Automatically migrate hosts connected to another MDM solution**. Click **Save** to save the change. -### Step 4: monitor your hosts as they migrate to Fleet MDM +### Step 4: Monitor your hosts as they migrate to Fleet MDM Once the automatic migration is enabled, Fleet sends a notification to each host to tell it to migrate. This process usually takes a few minutes at most.