Ante, Author at XOAP https://xoap.io/author/ante/ Platform for IT infrastructure and workplace automation Wed, 04 Mar 2026 08:05:11 +0000 en-US hourly 1 https://xoap.io/wp-content/uploads/2023/11/cropped-favicon-32x32.png Ante, Author at XOAP https://xoap.io/author/ante/ 32 32 Automating Amazon DCV deployment with XOAP https://xoap.io/automate-amazon-dcv-deployment/ Mon, 18 Aug 2025 13:05:47 +0000 https://xoap.io/?p=25167 Spin up a fully functional Amazon DCV environment efficiently. Reduce setup time, ensure consistency and enable rapid scaling.

The post Automating Amazon DCV deployment with XOAP appeared first on XOAP.

]]>

Table of contents

Amazon DCV (formerly NICE DCV) offers a high-performance, secure solution for delivering remote desktops and 3D applications. However, setting up DCV infrastructure manually can be time-consuming and prone to errors.

This blog post walks you through the automation process using AWS tools and XOAP to simplify the deployment of Amazon DCV.

How does it work?

Using prebuilt scripts, XOAP’s Image Management module and the Scripted Actions feature, you’ll spin up a fully functional Amazon DCV environment efficiently, reducing setup time, ensuring consistency and enabling rapid scaling in the cloud.

You can test everything in this tutorial for free, as both Image Management and Scripted Actions are available in XOAP’s free plan. Just create your account first.

The Amazon DCV deployment will take five steps:

  1. Download a script from AWS.
  2. Change the username in the script and upload it to XOAP.
  3. Create a connection to your AWS environment.
  4. Prepare your image for DCV deployment with Image Management.
  5. Spin up the DCV infrastructure with Scripted Actions.

Let’s go into the details now.

Step 1: Downloading script from AWS

Download the script from the official AWS GitHub repository here. You can find the documentation in the AWS Administrator Guide.

Step 2: Uploading script to XOAP

Now, let’s edit the script quickly before uploading it:

• Remove the first and last lines of code: <powershell> and </powershell>.

• Replace the placeholder “USERNAME” in line 51 with a valid username.

• Remove the comments from lines 49 to 52 (optional, but considered a good practice).

To upload the script, open your XOAP Workspace and go to the Resources area in the left-side menu. Click + New Resource, then simply drag and drop the script. Click Next and Save.

ℹ For more information on the script’s syntax, click here.
ℹ The DCV license is free on EC2, with a required S3 policy.

Follow the Amazon DCV automation video tutorial
This video may not load due to your cookie preferences. Adjust your cookie settings or watch it directly on YouTube.

Step 3: Creating a connection to your AWS environment

In XOAP, connections are used to deploy image definitions, as well as to provision and configure cloud and on-premises environments.

• Go to Connections in the left-side menu.
• Click + New Connection.
• Select AWS as the provider and choose the connection type.
• If you’re using the AWS-Access Key type, provide your Access Key ID, Secret Access Key and Account ID.
• Click Confirm to save the connection.

Step 4: Preparing image for DCV deployment

The next step is Image Management. It’s a custom image automation module that can be found in your XOAP Workspace.

First, create a provisioner:

• Click on Image Management, then click on Provisioners in the drop-down menu.
• In the Provisioners area, click + New Provisioner.
• Under Select Type, choose PowerShell Script.
• Under Source File, select Install-DCV.ps1, the script you uploaded to XOAP.
• Enter the mandatory information and click Confirm.

Create a provisioner | Amazon DCV automation | XOAP
Adding a provisioner in XOAP

 

Now, add that provisioner to a group:

•  Go to Image Management > Provisioner Groups.
•  Click + New Provisioner Group and select the provisioner you’ve created from Available Provisioners.
•  Enter the details and click Save.

Add the group to a provisioner role:

•  Go to Image Management > Provisioner Roles.
•  Click + New Role and select the group you created from Available Provisioner Groups.
•  Enter the details and click Save.

Note:

Each XOAP Workspace is equipped with Operating Systems that can be used as templates for further customizations. Operating system availability depends on the region and may vary. If your region is not available and you would like to adjust the operating system, you can add additional ones as needed.

The same applies to Builders, which define the connection being used, the region, the size of the VM defined to build the image and additional optional settings. You can create them before the next step or add them while defining the Image Definition.

• Now go to Image Management > Image Definitions and click + New Image. Here you will create your image – see screenshot below as a reference. If you need help creating the image, watch this short video tutorial.

Creating an image


Once your image is created, it will appear in Image Definitions.

• Click the three dots on the right in the image’s row, then click Run.

You can track the progress of the Image Definition build by either clicking on the status badge or by clicking on Runs in the upper right corner.

Once the run is finished, in the Image ID field, you will see the ID as ami-xxxxxxxxxxxxxxxxx.
It’s good to save the image ID now, as you will need it to spin up you DCV infrastructure later.

Important:
• If you don’t have it in your XOAP Workspace already, download the EC2 provisioning script ⬇ below and upload it to the Resources area, just like you did with the first AWS script.

Tutorial continues below
Download illustration

Download the EC2 provisioning script

By downloading, you accept the XOAP privacy policy and will receive product information from us.

Step 5: Spinning up DCV infrastructure

Now that you’ve uploaded the EC2 provisioning script to Resources, let’s move to Scripted Actions.

You will find this feature in your XOAP Workspace under the Platform Management module, which helps you automate hybrid infrastructures and cloud workflows.

• Go to Platform Management > Scripted Actions and click + New Scripted Action.
• Enter a Name for this scripted action.
• Under Choose a script from Resources, select the EC2 provisioning script.
• Click Next.

Create a scripted action | Automating Amazon DCV deployment | XOAP
Creating a scripted action


• Edit script parameters as shown below.

Important:

Under AMI_ID, use the Image ID from your Image Definition run. Specify the region where you want the EC2 instance to be created, along with the SUBNET_ID of the VPC where you want the instance to be placed. Make sure you choose the same region that was specified in your Image Definition. Otherwise, the AMI won’t be found, as they are region-specific.

Editing script parameters


• When everything’s ready, click Next.

• Select AWS from the Connections table and click Next. 

• In the final scripted action creation step, you can schedule your scripted actions. We can skip that for now, so just click Finish.

The scripted action is now created and you can run it the same way you ran your Image Definition. If you want to track the progress, click on the status badge right next to the scripted action. Once the run is finished, the DCV will be ready.

You can find all the information necessary for connecting to the DCV in the scripted action’s log. To access the log, click the three dots on the right side in the scripted action’s row and click View log.

Scripted action log | Automating Amazon DCV deployment | XOAP
Example of a scripted action’s log

To connect to the DCV, you can use web access or the Amazon DCV client, which is available for download from AWS. Be mindful of the required Security Group rules when connecting. Direct access to the instance will be required (for web access, you will need a public facing instance).

Alternatively, you can deploy the Amazon DCV client to your endpoints worldwide using XOAP’s Application Management module. Application Management automates and simplifies software packaging and delivery to any device. This way, you can easily create a remote access solution for your endpoints.

👉 Did we miss something? If you need help using XOAP to automate Amazon DCV deployment, just book a call 📅 and our engineers will walk you through it.

More about XOAP:

→ More on Application Management
→ Automating your entire AWS operations
→ Standardized image automation across platforms
→ Scripted Actions for centralized script management

Start automating your cloud infrastructure with XOAP

Start for free
Book a demo

The post Automating Amazon DCV deployment with XOAP appeared first on XOAP.

]]> How to spin up multiple VMs for Azure with Scripted Actions https://xoap.io/how-to-spin-up-multiple-vms-for-azure/ Tue, 07 Jan 2025 14:32:31 +0000 https://xoap.io/?p=17894 This article shows you how to spin up multiple Azure VMs from only one location. It's much simpler than you think!

The post How to spin up multiple VMs for Azure with Scripted Actions appeared first on XOAP.

]]>

Table of contents

Businesses are under constant pressure to deploy virtual machines (VMs) quickly and efficiently to meet changing demands and optimize cloud resource utilization. Managing these deployments across diverse platforms like Azure and AWS often introduces complexity and consumes valuable time.

To address these challenges, adopting a streamlined and automated approach is critical. This article highlights how XOAP’s Scripted Actions leverage the power of PowerShell to automate the provisioning of multiple VMs. By integrating this solution into their infrastructure, organizations can reduce manual workload, accelerate deployment cycles, and enhance their operational flexibility in managing cloud environments.

Quick VM deployment to Azure: Automate with Scripted Actions

With XOAP, deploying multiple virtual machines to your Azure subscription is a straightforward process that requires just three simple steps:

  1.  Add a Connection to your Azure subscription
  2.  Create a scripted action with defined parameters
  3.  Run the scripted action to deploy multiple VMs

Step 1: Add a Connection to your Azure subscription

To start, check if you’ve added a connection to your Azure subscription. If this hasn’t been set up yet, navigate to the Connections section in XOAP. Click the green plus (+) button to create a new connection. Follow the prompts to link your Azure subscription to XOAP securely.

Once the connection is established, you can proceed with the next steps.

Establish connection

In the “Add New Connection” slide-out panel, enter all the required connection details and click Save to complete the setup.
 

Save the setup

If you need additional guidance on adding a connection in XOAP, feel free to visit our documentation page.

Step 2: Create your scripted action

Next, navigate to Platform Management and select Scripted Actions. In the upper-right corner, click the green plus (+) button to create a new Scripted Action.

Add your scripted action

Give your Scripted Action a name and select the “az-ps-create-multiple-vm.ps1” script from the resources. Optionally, you can add tags and a description to organize and document your scripted action. You can get the script at the end of this blog. 
 

Select script from resources

In the second step, define your parameters. Some parameters are mandatory and must be provided, while others are optional. These optional parameters allow you to customize the VMs according to your specific requirements.

Edit your parameters

Explanation of Key Fields:

Number of VMs: Specifies the number of virtual machines you want to deploy.

Name Prefix: Sets the initial part of the VM names. For example, if your prefix is XOAPDemoVM, the script will automatically generate names like XOAPDemoVM001, XOAPDemoVM002, etc., by incrementing the numbering.

Digits: Defines how many digits should follow the name prefix. For example, 3 digits will result in names like XOAPDemoVM001.

PublicIpAddress: When enabled, creates a public IP address for each VM with the name format NamePrefixXX-PublicIP.

Image: If you’re using XOAP Image Management for creating images, you can retrieve the image ID from the run logs.

View key fields

Step 3: Complete your setup

In the third step, select your connection and click Finish to complete the setup.

Finish your scripted action setup

The final step is to run the Scripted Action you created. Locate your Scripted Action in the table, open the action menu, and select Run.

Run your script

The Scripted Action will progress through the Queued and Running phases. Once completed, its status will change to Success, and you will be able to find your VMs in the specified Resource Group.

Find your VMs in Resource Groups in Azure

Get more control over cloud resource management

XOAP’s Scripted Actions are great for automating the deployment of multiple virtual machines on cloud platforms like Azure and AWS. By leveraging PowerShell scripting, it delivers greater flexibility and control over cloud resource management. This approach simplifies the deployment process, reduces complexity, and saves time, enabling IT teams to concentrate on strategic projects rather than manual configurations. Adopting automation with Scripted Actions not only improves cloud operations but also prepares your organization to scale and adapt to future technological advancements.

📚 Additional resources for Scripted Actions: 

→ Scripted Actions tutorial: Step by step
→ Top 4 use cases for Scripted Actions
→ Cross-platform cloud automation with Scripted Actions
→ Scripted Actions documentation

Get the free script on GitHub →

Want us to deliver scripts directly to your inbox?

By subscribing, you accept the XOAP privacy policy and will receive product information from us.

The post How to spin up multiple VMs for Azure with Scripted Actions appeared first on XOAP.

]]> Tutorial: How to troubleshoot DSC compliance? https://xoap.io/tutorial-how-to-troubleshoot-dsc-compliance/ Mon, 02 Dec 2024 15:29:51 +0000 https://xoap.io/?p=17326 Learn how to troubleshoot DSC compliance with XOAP's step-by-step guidance for immediate resolution. Optimize your configurations easily.

The post Tutorial: How to troubleshoot DSC compliance? appeared first on XOAP.

]]>

Table of contents

Troubleshooting DSC compliance can feel like a real challenge, especially when things don’t seem to be working the way they should. But don’t worry—by keeping things simple and following a few key steps, you can get things back on track.

It’s all about simplifying your configurations, automating testing, improving your logging, doing regular audits, and maintaining documentation. With a methodical approach, many of the common compliance issues can be tackled and resolved. In this blog, we’ll show you how to troubleshoot DSC compliance easily. 

Why troubleshooting DSC compliance is so challenging

Troubleshooting DSC compliance can be complex due to several reasons:

Extensive environments

The complexity of DSC configuration files is a significant challenge, particularly in extensive environments with numerous nodes and a myriad of configurations. As the system grows and becomes more multifaceted, identifying the root cause of issues becomes increasingly difficult. The interdependencies between different configurations can obscure the source of the problem, complicating efforts to maintain compliance.

Another challenge arises from the potential for systems to slip into an inconsistent state. This can occur due to configuration drift or unsuccessful application of configurations. When the actual state of the system diverges from the desired state, discrepancies emerge that can reduce effectiveness and reliability.

Error diagnostics and network issues

Error diagnostics add another layer of difficulty to troubleshooting DSC compliance. The error messages provided by DSC can often be cryptic or insufficiently detailed, making it challenging to determine the precise cause of an issue. Without clear diagnostics, addressing and resolving the problem becomes significantly more challenging.

Network and connectivity issues also play a critical role in compliance challenges. Since DSC relies on network connectivity to access configurations from a central repository, problems such as network latency or disconnections can hinder proper application of configurations. These issues can cause systems to fall out of compliance if they cannot access the necessary configuration data.

Resource conflicts and host-specific issues

Resource conflicts present another challenge. DSC configurations may include resources that conflict with each other—for example, two resources might attempt to set the same property of a system setting in different ways. This can lead to unpredictable system behavior and complicate compliance efforts.

Host-specific issues further complicate the troubleshooting process. Variations in target node environments, such as differing operating system versions or installed software, can result in different outcomes from identical configurations. This specificity requires extra attention to ensure consistency across all nodes.

Versioning and logging

Changes in versioning and updates, such as those involving PowerShell or DSC module versions, can also introduce challenges. Such changes may bring compatibility issues or bugs that disrupt compliance. Staying up-to-date while maintaining stability can become a balancing act that requires careful management.

Finally, the challenge of insufficient logging complicates deeper analysis. Although DSC provides some logging capabilities, diagnosing complex issues often requires more detailed logs. Without additional configuration to enhance logging detail, these issues can be difficult to detect and resolve.

How to troubleshoot DSC compliance

Before we show you how to troubleshoot DSC compliance, create your own XOAP workspace. XOAP’s module, config.XO (Configuration Management), helps you create, organize, and apply your DSC configurations. Using config.XO, you can easily create DSC configurations with GUI and make versions of the created configurations.

This tutorial is also available as a YouTube video:

This video may not load due to your cookie preferences. Adjust your cookie settings or watch it directly on YouTube.

Step 1

To use the Configuration Wizard, click on Configuration Management, and then Configuration. Here, you can create a new configuration or you can edit an existing one.

Step 2

Here you can configure your DSC configuration and create a version for every change that you did.

Step 3

Using Configuration Management Group, you can apply different versions to your Nodes. Just apply the desired version to the group and assign nodes:

Step 4

Using these XOAP options enables you to simplify the creation of DSC, create versions, and control which nodes should get specific versions of the configuration. 

If you check the Groups table, you can see how many nodes are compliant in your group:

More information about the specific state of the node can be found under Configuration Management nodes.

There are 3 states of node status:

  • Compliant: Node is compliant with all DSC resources applied to it
  • Non-compliant: At least one DSC resource is not applied to the node
  • Running: DSC configuration is currently applying

Step 5

Using the Last activity information, you can check that the communication between XOAP and your node is working.

Clicking on the Compliant state, you can see the compilation history.

Step 6

Here you can see all compilation status changes in the last 14 days. With the status, you can see which configuration and which version is applied at a specific time.

By clicking on Compliant status, you’ll be able to see the status of applied DSC resources:

In case of non-compliant status, you can also check logs:

Another way to check the status is to open the node details:

Under Powershell DSC you can check for all compliance issues:

In case of communication issues between XOAP and your servers, make sure that you allow communication with API.XOAP.IO by port 443 and that you whitelisted our IP addresses on your firewall. Information about IPs and API can be found on the dashboard:

Why use XOAP to troubleshoot DSC compliance

XOAP’s config.XO module provides a user-friendly way for creating, organizing, and applying DSC configurations through a graphical interface. This intuitive approach allows users to easily generate configurations and manage different versions, addressing the complexities and potential errors stemming from manual scripting. By using the Configuration Wizard, users are empowered to create and modify configurations, so changes are well-documented and easily reversible.

The ability to apply different configuration versions to specific nodes or groups of nodes offers significant flexibility. This helps manage resource conflicts and host-specific issues by ensuring that the right configurations are applied to the appropriate nodes. By organizing nodes into groups and assigning configurations accordingly, XOAP simplifies the management of large environments and improves consistency across deployments.

XOAP also provides monitoring capabilities, allowing administrators to track compliance status among nodes. Moreover, the platform’s logging and compilation history features offer valuable insights into past activities and changes, helping users diagnose and resolve issues promptly.

Communication between XOAP and the nodes is crucial for maintaining compliance, and the Last Activity information guarantees this connectivity remains intact. Also, detailed logs and node details offer deep insights into specific compliance issues, enabling administrators to take targeted actions to rectify problems and secure optimal system performance.

 

Stuck trying to troubleshoot DSC compliance? Just use XOAP
Need more help? Contact us here

Troubleshoot DSC compliance now

The post Tutorial: How to troubleshoot DSC compliance? appeared first on XOAP.

]]> Free BitLocker module: Encrypt HD disk easily https://xoap.io/free-bitlocker-module-encrypt-hd-disk-easily/ Thu, 07 Nov 2024 09:23:25 +0000 https://xoap.io/?p=16850 Implement and manage BitLocker on Windows 10/11 and Windows 2022 Datacenter (server solution) using XOAP's free BitLocker module.

The post Free BitLocker module: Encrypt HD disk easily appeared first on XOAP.

]]>

Table of contents

Safeguarding sensitive data is more crucial than ever, particularly as organizations increasingly rely on mobile devices and remote work environments. Among the array of security measures available, BitLocker stands out as a powerful encryption tool designed to protect data stored on Windows devices. However, many organizations face challenges in effectively deploying and managing BitLocker across their systems.

You can streamline the deployment of BitLocker using XOAP’s Configuration Management module. Configuration Management simplifies the implementation of BitLocker through Desired State Configuration (DSC), allowing IT administrators to automate and standardize encryption across managed devices.

DSC ensures that systems remain compliant with organizational policies, reducing the risk of misconfigurations and ensuring that all devices are appropriately protected.

In this blog post, we will guide you through the process of implementing and managing BitLocker on Windows 10/11 (client solution) and Windows 2022 Datacenter (server solution).

With XOAP, you can begin the deployment process immediately. Simply create a free XOAP account and follow the steps below.

You can also download our BitLocker module and put it to use yourself.

Windows 10 and 11 (Client solution)

To encrypt a virtual machine disk using BitLocker, first you will need to enable Trusted Platform Module (TMP) in Hyper-V Manager.

To do this, open the VM settings and click on Security. In the Encryption Support section, check the Enable Trusted Platform Module box. Click here for detailed instructions.

Moving on to Configuration Management. If you haven’t yet, create a free XOAP account and go to your Workspace. In Configuration Management, create a new configuration or open an existing one.

XOAP's BitLocker tutorial - client solution - step 1

Click Add resources.

XOAP's BitLocker tutorial - client solution - step 2

Select XOAPBitlockerDSC and add EnableBitlocker-DSC resource from XOAPBitlockerDSC-Module.

XOAP's BitLocker tutorial - client solution - step 3

Save your configuration.

If the configuration is saved and compiled (this might take a few moments), you will see your DSC resources when you click on the View code option in your configuration.

XOAP's BitLocker tutorial - client solution - step 4

Now, go to Groups in Configuration Management and create a new group or choose an existing one.

In the Edit group screen, attach your configuration for BitLocker to that group.

XOAP's BitLocker tutorial - client solution - step 5

Download the group registration script and run it on your machine.

Bitlocker Recovery Key will now be stored within your Microsoft Entra (if your device is already joined) and locally on the second drive you chose in the configuration. 

 

Windows Server 2022 Datacenter (Server solution)

For the server solution, first you will need to install prerequisites with the PSDesiredStateConfiguration resources.

Specifically, you’ll need to enable the WindowsFeature and WindowsFeature RSAT-Feature-Tools-Bitlocker. These features are essential for ensuring that BitLocker operates effectively on your Windows Server 2022 Datacenter environment.

XOAP's BitLocker tutorial - server solution - step 1

In XOAP, this will involve setting up two distinct DSC resources: one for the WindowsFeature and another for the RSAT-Feature-Tools-Bitlocker WindowsFeature. See screenshots below.

XOAP's BitLocker tutorial - server solution - step 2
Bitlocker WindowsFeature
XOAP's BitLocker tutorial - server solution - step 3
RSAT-Feature-Tools-Bitlocker WindowsFeature

Please note:

• If you need to encrypt the system drive (e.g., C), you should use the DSC resource xBLBitLocker from our module as done here.

• To automatically enable BitLocker on fixed or removable drives, you should use the DSC resource xBLAutoBitLocker from our module. It does not work on operating system drives, but requires the OS to be encrypted. If you have multiple drives, use both DSC resources as done here.

Finalizing the configuration

Once you’ve completed your BitLocker configuration and linked it to a group within Configuration Management, download the group registration script associated with your BitLocker configuration.

Run the script on your machine, and after the required reboots, your drives should be successfully encrypted by BitLocker. ✅

Outcome

Windows 10 and 11 (Client solution).

If the device is joined to the work (or school) organization’s Microsoft Entra ID, then the VM and the BitlockerKey will be stored in My Account > Devices area.

XOAP's BitLocker tutorial - outcome - example 1

 

XOAP’s Configuration Management 

 

XOAP's BitLocker tutorial - outcome - example 2

 

Locally on the VM (ResourceCount can vary)

 

XOAP's BitLocker tutorial - outcome - example 3
XOAP's BitLocker tutorial - outcome - example 4

Windows Server 2022 Datacenter (Server solution)

Backing up the Recovery Key is essential for ensuring you can regain access to your data. You can do this using the Windows option available in the Manage BitLocker settings.

 

XOAP's BitLocker tutorial - outcome - example 4

Begin the deployment process immediately

So, are you ready to try it with the XOAP automation platform? Just follow the steps above and you’ll be done in no time. The BitLocker module is directly available in your free XOAP Workspace. If you prefer to do this manually, download the BitLocker module. 

Download illustration

Download BitLocker module

By downloading, you accept the XOAP privacy policy and will receive product information from us.

The post Free BitLocker module: Encrypt HD disk easily appeared first on XOAP.

]]> Cross-platform cloud automation with Scripted Actions https://xoap.io/cross-platform-cloud-automation-with-scripted-actions/ Tue, 01 Oct 2024 10:34:47 +0000 https://xoap.io/?p=16021 Feeling overwhelmed managing scripts across Azure, AWS, and Google Cloud? Let's see how XOAP's Scripted Actions can make cross-platform cloud automation a breeze!

The post Cross-platform cloud automation with Scripted Actions appeared first on XOAP.

]]>

If you’re managing and executing scripts across multiple cloud platforms like Azure, AWS, and Google Cloud, you know how challenging it can be. It often feels like a never-ending cycle of repetitive tasks and inconsistencies, which can be frustrating.

We get it, and we want to help. XOAP’s Scripted Actions feature is here to make your life easier. It allows you to run a single script across various cloud connections, reducing the hassle of managing multiple environments. This means less time spent on repetitive work and more consistency in your operations.

If you’re dealing with these challenges, this quick guide is designed for you! Have a look.

🤔 Want to know what else you can do with Scripted Actions? Find out here: Top 4 use cases for Scripted Actions 

How to achieve cross-platform cloud automation with Scripted Actions

First, if you don’t have a XOAP account yet, you can create a free one here. 

Before creating your scripted action, add cloud provider connections to your Workspace. Go to Connections and then click +.

Add your cloud provider connections to your Workspace

Insert the required data into the connection you want to add.

To know how to add a connection, visit our documentation.

Insert the required data

In the next step, you need to upload your PowerShell scripts to the Resources section to use them with the Scripted Action feature. To do that, go to Resources and click +.

Upload your PowerShell scripts to the Resources section

Follow the steps to upload your scripts. For more details about Resources, visit this documentation page.

Now you’re ready to create your scripted actions! Navigate to Platform Management and click on the Scripted Actions navigation item. Then click + to create a new scripted action.

Create your Scripted Action

Fill in the Details data, select the script from resources and the specific resource version, and click “Next”. 

Fill out what's needed

Add script parameters values and click “Next”. 

Add script parameters

In the Connections step, select the cloud provider(s) you want to run the scripted action on and click “Finish”.

Select cloud providers

Now the scripted action is ready to be run. Find your scripted action in the Scripted Actions table, click on the action menu and select “Run”.

This will execute the script to all selected cloud provider connections. In this example, the new AWS Account will be created on all selected connections.

If you’d like to schedule the created scripted action, please have a look at the Schedules area in XOAP.

Run the Scripted Action you've created

⚠ Implement cross-platform solutions ASAP

The Scripted Actions feature of the XOAP platform represents a significant advancement in multi-cloud management. From a technical perspective, it simplifies the complexities of operating across diverse cloud environments by allowing a single script to be executed seamlessly on various customer infrastructures. This innovation not only improves operational efficiency but also ensures consistency, reduces the risk of human error, and provides scalability in managing cloud resources.

With Scripted Actions, XOAP empowers technical teams to focus more on innovation and less on repetitive cloud management tasks, thus driving greater productivity and strategic growth. 

📌 You may also be interested in:

Scripted Actions documentation
Step-by-step guide to Scripted Actions
Video tutorial: How to create and run Scripted Actions

Use Scripted Actions for free

The post Cross-platform cloud automation with Scripted Actions appeared first on XOAP.

]]> How to (re)deploy your Windows OS with XOAP https://xoap.io/how-to-deploy-windows-os-with-osdcloud-amp-xoap/ Wed, 24 Jul 2024 11:41:47 +0000 https://xoap.io/?p=14798 Combine XOAP with OSDCloud for simplified OS deployment without needing additional backend infrastructure.

The post How to (re)deploy your Windows OS with XOAP appeared first on XOAP.

]]>

Table of contents

Windows OS deployment is a critical task in IT management, involving the installation, customization and configuration of the Windows operating system on client computers within an organization. This process makes sure that all systems are standardized, secure and up-to-date with the necessary software and configurations to meet business needs.

However, for many, Windows OS deployment poses challenges – we’ll explain why. After that, we’ll show you how to solve them by combining XOAP with OSDCloud.

Why deploying Windows OS is not an easy task

Deploying Windows operating systems presents several challenges for IT administrators:

Customization complexity: Deploying an operating system across numerous client computers often requires tailoring settings and software to meet diverse user and departmental needs. This demands significant effort to ensure the deployment process accommodates various hardware configurations, applications, and user preferences.

Consistency and standardization: Ensuring that OS deployment is consistent across all client machines is crucial. Inconsistencies can arise from differences in hardware, prior configurations, and user-installed software. While maintaining a standardized environment enhances manageability, achieving this uniformity can be challenging.

Security and compliance concerns: Ensuring that all deployed systems are secure and compliant with organizational policies and regulatory requirements is a perpetual concern. This includes configuring security settings, installing necessary patches and updates, and verifying that all systems meet the required compliance standards.

Post-deployment support: Following the initial deployment, continuous support is crucial to resolve any issues that arise. This includes troubleshooting, system updates, and user assistance. Providing adequate support is essential for maintaining productivity and ensuring system health.

To address these challenges, consider combining XOAP with the OSDCloud solution.

OSDCloud facilitates the deployment of Windows 10/11 over the internet using the OSD PowerShell Module. The process involves booting into WinPE, where the OSDisk is wiped and partitioned. Afterward, the Windows Operating System is downloaded from Microsoft Update (using CuRL) and then staged (expanded) on the OSDisk. More information can be found on the OSDCloud website. 

Let’s see how you can use OSDCloud easily without the hassle of installing additional modules or dependencies. ⬇

Simplified deployment with XOAP & OSDCloud

First, create a free XOAP account if you don’t have one yet. (No credit card required!)

Log in to your Workspace and navigate to Application Management > Groups.

Find the group named OSDCloud and select Edit. 

OSDCloud and XOAP OS deployment example 1

In the group editing window, expand the OSDCloudImageCreation application and configure the parameters to define your OSD image.

OSDCloud and XOAP OS deployment example 2

Besides the standard PSADT parameters, you can define the following OSDCloud-related parameters:

  • Driver: Configures whether drivers should be installed directly from the manufacturer’s site. ➜ Select * to install all drivers, or None to not install any.
  • OSActivation: Select between Volume and Retail.
  • OSVersion: Select the desired OS version.
  • OSBuild: Select the build of the desired OS.
  • OSEdition: Select the edition of the desired OS.
  • OSLanguage: Select the language.
  • unattendFileLocation: The location of the unattended file used to configure the OS. ➜ If you do not define this parameter, a generic unattended file will be used, which will create two users, “Admin” and “User,” with the generic password “password.”
  • XOAPConfigurationGroup: The name of the configuration group to which the node should be registered. ➜ You can find the available configuration groups in your XOAP Workspace > Configuration Management > Groups.
  • XOAPWorkspaceID: The Workspace ID can be found on the main dashboard under “Account Information” or in your URL:
OSDCloud and XOAP OS deployment example 3

IMPORTANT:

For security reasons, always use your own unattend.xml file. If you use the generic one, make sure to change the passwords for the users after deployment is complete.

If you are using your own unattend file, please include the following line of code in the "<settings pass="specialize">" section:

<Path>powershell.exe -NoProfile -ExecutionPolicy Bypass -File "C:\Windows\XOAP.ps1"</Path>

See a code example of the generic unattend.xml with the code line for running XOAP.ps1 file below:

OSDCloud and XOAP OS deployment example 4

The XOAP.ps1 file is used to register your client to your XOAP Workspace during OSD.

Once you have defined all parameters, click Save in the Edit Group window.

The next step is to run the role installation script on the machine where the installation ISO should be created.

To do this, go to Application Management > Roles. Find the OSDCloud role, navigate to the action menu, and download the installation script.

OSDCloud and XOAP OS deployment example 5

Copy the script to your desired machine, run PowerShell as an administrator and run the script.

This will install all prerequsites for OSDCloud and the creation of the ISO files.

After the script runs successfully, you should have two ISO files in C:\OSDCloudWorkspace:

The last step is to create a bootable USB stick that can be used to deploy your laptops. You can use the New-OSDCloudUSB function. Just run it from the local PowerShell (with Admin rights), select a USB device attached to your machine and wait for it to finish.

For advanced configurations and adjustments, you can download the OSDCloudImageCreation PSADT package from the example above and modify it with additional parameters to suit your needs. More information about this OSD function can be found on the OSDCloud website. 

Consistent & standardized OS deployment

By combining XOAP and OSDCloud, you can easily prepare new machine deployments and automatically register them in XOAP for further management. This way you’ll have a consistent and standardized OS deployment without the need for any additional backend infrastructure.

By using our config.XO and application.XO modules, you can install all your standard applications and apply required system and user configurations or security settings.

For this purpose, have a look at our STIG and CIS DSC modules (also available on GitHub), which you can implement into your configurations. If you want to learn more or need additional help getting started with specific use cases, we are available for a free demo. 👋

Start for free

The post How to (re)deploy your Windows OS with XOAP appeared first on XOAP.

]]> Quick fix: Citrix Virtual Delivery Agent security issue https://xoap.io/quick-fix-citrix-virtual-delivery-agent-security-issue/ Mon, 22 Jul 2024 09:51:08 +0000 https://xoap.io/?p=14536 Need help with Citrix Virtual Delivery Agent security issue? It can be resolved sooner than you think – all through one platform.

The post Quick fix: Citrix Virtual Delivery Agent security issue appeared first on XOAP.

]]>

Table of contents

Citrix Virtual Delivery Agent (VDA) allows you to access your work applications and desktops from any device, whether you’re at home, in the office or on the go. It connects your computer or device to the servers where your work information and programs are stored, making sure everything runs smoothly and remains secure.

VDAs are installed on the machines (either physical or virtual) that host your work apps and desktops. This software uses advanced technology to provide a high-quality experience and manages your work sessions to connect and stay connected easily. Whether you’re accessing a full desktop or just a particular application, VDAs make it possible.

The main benefits of using Citrix VDAs include the ability to work remotely with the flexibility to use various devices, increased security by centralizing your data and easier IT management thanks to centralized control of applications and desktops. VDAs are available in two types: Desktop VDAs for accessing full virtual desktops and Server VDAs for accessing shared desktops or specific applications.

In this blog, we’ll show you how to solve the latest security issue for Citrix Windows Virtual Delivery Agent. Take a look. ⬇

What you need to do first

To set up a VDA, you need to install the software on the machine hosting your applications or desktops and connect it to the Citrix server that manages everything. You also need to configure settings and policies through a central management tool. VDAs are compatible with various versions of Windows and Linux operating systems, but you’ll need sufficient CPU, memory and storage, along with a reliable and fast internet connection for optimal performance.

Currently, there’s an open Security Bulletin CVE-2024-6151 for Citrix Windows Virtual Delivery Agent.

The vulnerability affects the following supported versions of Windows Virtual Delivery Agent:

Current Release (CR)

  •     Citrix Virtual Apps and Desktops versions before 2402

Long Term Service Release (LTSR)

  •     Citrix Virtual Apps and Desktops 1912 LTSR before CU9
  •     Citrix Virtual Apps and Desktops 2203 LTSR before CU5

To resolve these security issues, you need to upgrade to one of the following versions:

Current Release (CR)

  •     Citrix Virtual Apps and Desktops 2402 and later versions

Long Term Service Release (LTSR)

  •     Citrix Virtual Apps and Desktops 1912 LTSR CU9 and later cumulative updates
  •     Citrix Virtual Apps and Desktops 2203 LTSR CU5 and later cumulative updates
  •     Citrix Virtual Apps and Desktops 2402 LTSR

Tackle the security issue with XOAP

One of the easiest ways to install a new version of the VDA is to use XOAP. We’re providing installation packages for VDA Workstation, VDA Workstation Core and VDA server.

Step 1: In your XOAP workspace navigate to Application Management > Groups, find the needed VDA group and in the action menu click on Edit.

VDA security issue solved by XOAP, Step 1

Step 2: This will open the group editing window. Expand the application installation settings and configure them as needed. When you’re done, click Save.

VDA security issue solved by XOAP, Step 2

Step 3: Then navigate to Configuration Management > Groups. Find the corresponding group with the assigned application role and click on the action menu and select “Copy registration command”.

VDA security issue solved by XOAP, Step 3

Step 4: Log in to your machine, run PowerShell as administrator and insert the registration command from the clipboard. This will apply the configuration, download the assigned applications and install them on your machine.

The registration script can be run on multiple machines in case you need to do a mass deployment.

VDA security issue solved by XOAP, Step 4

🔐 Better safe than sorry

It’s important to stay updated with the latest version of Citrix Virtual Delivery Agent (VDA) to address security concerns, meet compliance and industry standards and benefit from improved stability and performance.

The latest updates often include patches that address known vulnerabilities. By updating, you significantly reduce the risk of exploitation by malicious actors.

Many industries have regulatory requirements that mandate the maintenance of up-to-date software to protect sensitive data. Keeping your software updated ensures compliance with these regulations.

Newer versions of software typically come with improvements that enhance system stability and performance, providing a better experience for users.

Moreover, vendors often discontinue support for older versions of their software. By updating to the latest version, you continue to receive technical support and updates from Citrix.

Updates often include new features and enhancements that can improve functionality and usability, allowing you to leverage the latest technological advancements.

Also, an updated VDA helps mitigate the risks of data breaches, unauthorized access, and other cyber threats that can have severe consequences for your organization.

Need more help with Citrix VDA? Book a quick demo with our expert. 🙋‍♂️

Solve the VDA issue for free

The post Quick fix: Citrix Virtual Delivery Agent security issue appeared first on XOAP.

]]> Quick fix: Citrix Workspace app security issue https://xoap.io/quick-fix-citrix-workspace-app-security-issue/ Mon, 22 Jul 2024 09:44:47 +0000 https://xoap.io/?p=14609 Affected by the Citrix Workspace app security issue? Let XOAP take over that burden. Easily install a new version.

The post Quick fix: Citrix Workspace app security issue appeared first on XOAP.

]]>

Table of contents

The Citrix Workspace app is a unified solution that provides access to virtual desktops, applications and other resources from a single interface. It can access all applications, desktops and files from one portal.

Moreover, the Workspace app has advanced security protocols to protect sensitive information. This includes multi-factor authentication and single sign-on capabilities.

Additionally, it provides cross-platform support, making it compatible with various operating systems such as Windows, macOS, iOS, Android and Linux.

Thanks to its enhanced graphics capabilities and performance optimizations, it provides a smooth user experience, even with demanding applications.

It also offers integrated file access, allowing users to access their files directly from the workspace without switching between different applications.

We cannot forget that the Citrix Workspace app promotes collaboration through built-in tools that facilitate communication and shared workspaces among team members, promoting productivity and teamwork.

Having thoroughly assessed all the advantages of this solution, we are fully prepared to effectively address its latest security issue. 🔐

What you need to do first

At the moment, there’s an open Security Bulletin CVE-2024-6286 for Citrix Windows Workspace App (addressed here).

The vulnerability affects the following supported versions of the Citrix Workspace app for Windows

Current Release (CR)

  •     Citrix Workspace app for Windows versions before 2403.1

Long Term Service Release (LTSR)

  •     Citrix Workspace app for Windows versions before 2402 LTSR
  •     Citrix Workspace app for Windows versions before 2203.1 LTSR CU6 Hotfix 2

To resolve these security issues, you need to upgrade to one of the following versions:

Current Release (CR)

  •     Citrix Workspace app for Windows 2403.1 and later versions

Long Term Service Release (LTSR)

  •     Citrix Workspace app for Windows 2402 LTSR and later versions
  •     Citrix Workspace app for Windows 2203.1 LTSR CU6 Hotfix 2 and later versions

Tackle the security issue with XOAP

The simplest way to install a new version of the Citrix Windows Workspace App is to use XOAP.

Step 1: In your XOAP workspace navigate to Application Management > Groups. Find the “XOAP Citrix Extension – Workspace App 2402 LTSR” group and click on Edit.

Workspace App issue solved by XOAP, Step 1

Step 2: This will open the group editing window. Extend the application installation settings and configure them as needed. When your’re done with the configuration, click Save.

Workspace App issue solved by XOAP, Step 2

Step 3: Then navigate to Configuration Management > Groups. Find the desired group, click on the action menu and select “Copy registration command”.

Workspace App issue solved by XOAP, Step 3

Step 4: Login to the machine you want to configure, run Powershell as administrator, and insert the command from the clipboard. This will apply the configuration, download the applications and install them on the machine.

Moreover, the registration script can be run on multiple machines, in case you need to do a mass deployment.

Workspace App issue solved by XOAP, Step 4

⚙ Stay on top of app updates

Installing the latest version of the Citrix Workspace app for Windows is crucial for addressing security issues, ensuring compliance and accessing new features and enhancements. By using XOAP, you can easily manage all aspects from one console.

The latest updates often include patches that address known vulnerabilities. By updating, you reduce the risk of exploitation by malicious actors.

Many industries have regulatory requirements that mandate the maintenance of up-to-date software to protect sensitive data. Keeping your software updated ensures compliance with these regulations.

Also, newer versions of software typically come with improvements that enhance system stability and performance, providing a better experience for users.

Keep in mind that vendors often discontinue support for older versions of their software. By updating to the latest version, you can continue to receive technical support and updates from Citrix.

The updates also introduce new features and enhancements that can improve functionality and usability.

That’s all for today! For more information or assistance, book a demo for guidance and support. 🤝

Solve the Workspace app issue for free

The post Quick fix: Citrix Workspace app security issue appeared first on XOAP.

]]> Quick fix: Citrix Provisioning security issue https://xoap.io/quick-fix-citrix-provisioning-security-issue/ Mon, 22 Jul 2024 09:39:33 +0000 https://xoap.io/?p=14539 Affected by Citrix security issues? Learn how to install a new version of Provisioning Services quickly and easily using XOAP.

The post Quick fix: Citrix Provisioning security issue appeared first on XOAP.

]]>

Table of contents

Citrix Provisioning Services (PVS) allows organizations to streamline their IT infrastructure by transforming traditional disk imaging processes into centralized management. This technology enables the creation and maintenance of a single image that can be streamed to multiple devices across the network, enhancing both efficiency and scalability.

PVS provisions systems directly from this centralized shared image, reducing the need for individual device storage and simplifying updates and management. When an update is necessary, changes can be made to the master image, and each connected device receives the updated version upon reboot, ensuring consistency and speed.

The principal advantages of using Citrix Provisioning Services include:

  • Simplified image management
  • Reduced storage requirements
  • Rapid deployment of updates and patches
  • Enhanced scalability.

By maintaining a single image, IT teams can rapidly deploy new systems and ensure uniform configurations across the entire network.

What about setup and maintenance?

Well, setting up Citrix Provisioning Services involves configuring a provisioning server to host the master images and setting up target devices that will stream the images. The target devices boot from this streamed image instead of relying on a local hard drive. This process requires configuring the network, setting up the provisioning server, and creating and maintaining the master images.

PVS is compatible with a range of operating systems, including various versions of Windows and Linux, and can be integrated with other Citrix solutions to enhance performance and management. For optimal operation, adequate network bandwidth, reliable storage solutions, and robust server infrastructure are essential to support the streaming process and maintain high performance.

Considering all of this, we’ll show you how to solve the latest Citrix Provisioning issue. 🛠

What you need to do first

Recently, an open Security Bulletin, CVE-2024-6150, was issued for Citrix Windows Provisioning. 

The vulnerability impacted the following supported versions of Citrix Provisioning:

Current Release (CR)

  •     Citrix Provisioning versions before 2402

Long Term Service Release (LTSR)

  •     Citrix Provisioning versions before 2203 LTSR CU5
  •     Citrix Provisioning versions before 1912 LTSR CU9

If you haven’t yet, you need to upgrade to one of the following versions to resolve these security issues:

Current Release (CR)

  •     Citrix Provisioning 2402 and later versions

Long Term Service Release (LTSR)

  •     Citrix Provisioning 2203 LTSR CU5 and later versions
  •     Citrix Provisioning 1912 LTSR CU9 and later versions

Tackle the security issue with XOAP

How to deal with vulnerabilities as soon as they arise? One of the easiest ways to install a new version of Provisioning Services is by using XOAP.

We provide installation packages for the Provisioning Services Console, Provisioning Services Server and the Provisioning Services Device.

Step 1: In your XOAP Workspace, navigate to Application Management > Groups. Find the required PVS group, and in the action menu, click Edit. This will open the group editing window.

Citrix provisioning security fix using XOAP, Step 1

Step 2: Expand the application settings and configure them as needed. When you’re done with the configuration, click Save.

Citrix provisioning security fix using XOAP, Step 2

Step 3: Navigate to Configuration Management > Groups. Find the desired group, click on the action menu, and select “Copy registration command”.

Citrix provisioning security fix using XOAP, Step 3

Step 4: Log in to your desired machine, run PowerShell as administrator and insert the command from the clipboard. This will apply the assigned configuration, download the applications, and install them on your machine.

You can run this registration script on multiple machines if you need to perform a mass deployment.

Citrix provisioning security fix using XOAP, Step 4

💡 The importance of regular patching

In conclusion, regular patching and updating of software such as Citrix Provisioning Services (PVS) offer several crucial benefits. These include improved security by addressing vulnerabilities, improved performance, stability through bug fixes and compatibility with evolving IT components.

Additionally, staying up-to-date with patches introduces new features, helps maintain compliance with industry standards and can ultimately lead to cost savings by preventing potential issues and minimizing the need for reactive troubleshooting.

Embracing a proactive approach to software maintenance not only safeguards your systems but also contributes to better end-user experiences and more efficient IT operations.

By using XOAP, you can easily achieve all of this from a single console! For extra help with Citrix PVS, you can always book a demo with our experts. 🤗

Start instant patching for free

The post Quick fix: Citrix Provisioning security issue appeared first on XOAP.

]]> Apply STIG security compliance in a few steps https://xoap.io/apply-stig-security-compliance-in-a-few-steps/ Thu, 11 Jul 2024 12:49:25 +0000 https://xoap.io/?p=14349 Learn how to quickly achieve STIG security compliance with XOAP. Follow our simple steps to improve your organization's security.

The post Apply STIG security compliance in a few steps appeared first on XOAP.

]]>

Table of contents

Implementing STIG compliance in your organization makes perfect sense. STIG (Security Technical Implementation Guide) is a set of security configuration standards and guidelines created by the DISA (Defense Information Systems Agency) to improve the security of DoD systems and data.

Moreover, STIGs are used to make sure that information systems are configured securely, in a standardized manner and that they comply with DoD policies and security best practices.

Today, we’ll guide you through a simple STIG implementation using XOAP automation platform. Let’s get started! 🛡

Avoid these STIG challenges with XOAP

Complexity, cost, frequent updates

Implementing STIGs comes with several challenges. Firstly, the detailed and comprehensive nature of STIGs can make it difficult to understand and implement all requirements correctly.

Secondly, implementing STIGs can be resource-intensive, requiring significant time, effort and expertise. Organizations may need specialized personnel to interpret and apply the guidelines correctly.

Furthermore, STIGs are frequently updated to address new vulnerabilities and evolving security threats. Keeping up with these updates and ensuring that systems remain compliant can be challenging for many organizations.

Interoperability issues, downtime, inspections

Applying STIGs can lead to compatibility or interoperability issues, especially in complex environments with a mix of newer and older systems or different operating systems and applications. Moreover, the implementation of STIGs can have operational impacts, such as system downtime or reduced performance, as configurations are changed and tested for compliance.

Lastly, maintaining thorough documentation to demonstrate compliance with STIG requirements can be burdensome. Organizations must be prepared for audits and inspections to verify compliance.

Despite these challenges, the implementation of STIGs is crucial for maintaining high-security standards within DoD systems and minimizing the risk of cyber attacks and vulnerabilities. And with the help of XOAP’s security standards compliance, it doesn’t have to be so complicated. 🔐

Achieve STIG security compliance in a few steps

To help you with the implementation of the STIG we’re regularly releasing STIG DSC modules on GitHub. You can use these modules to deploy STIG on your infrastructure. The easiest way to do that is to use our Configuration Management.

If you’re new to XOAP, you can create your free account. Once your account is created, use our DSC Configuration Wizard to create your STIG DSC configuration.

Navigate to Configuration Management > Configurations and click the green + to create a new configuration.

Create a new configuration in XOAP

In the DSC Configuration wizard, specify a name and a description for your configuration. After that click “Add Resources” to add STIG resources.

Add STIG resources

In the “Create New Resource”  window select the STIG module you want to use, the module version and the specific resource which you want to apply. The resources are named according to their use case. The only thing you need to provide is the Resource Display Name.

⚠ Resource names must be unique within a DSC configuration!

Name the resource

Once you are ready with adding resources click “Save” in the “Create New Resource” window. If you need to add more resources, repeat the same steps for all needed resources. To create the configuration, click “Save” in DSC Configuration Wizard, provide a “Version Message” in the “Save Configuration” window and click Save.

Save the configurations you made

Saving the configuration will start a background job that compiles the configuration. In approximately 10 to 15 minutes, your configuration will be ready. While waiting we can create a new group that this configuration will be assigned to.

To create a new group, go to Configuration Management > Groups and click the green + button. In the “Add Group” window provide a name, select the saved Configuration with the desired version and choose a policy. If you want, you can assign an Application Role (from the Application Management module) and provide Tags as needed.

Add group and all details

When you are ready, click save in “Add Group” window.  To register a node in XOAP and to automatically apply the created STIG configuration to the node, find the group in the Groups table, click on the action menu and select “Copy registration command”.

Copy the registration command

This will copy the necessary registration command into your clipboard. The next step is to go on your Node, run Windows PowerShell as administrator, and paste and run the command.

After running the command, the configuration will be downloaded and applied:

Run this command

Once finished your Node will be visible in the Nodes area in Configuration management. In case of any problems, you can easily detect which configuration item is the reason, and which specific configuration is not compliant.

To get that information, go to Configuration Management > Nodes, find your Node, click the “Action Menu” and select “Details”.

Check the details of Nodes

In the “Current Status” window, in the PowerShell DSC menu, you can find information about successfully applied configurations, and resources within the configuration that are causing issues:

See the details of the current status

Compliance issues show you details about resources that could not be applied or that caused issues. From here on you can see which resources need to be adjusted to get a compliant state.

Check compliance issues

As many settings of the STIG recommendations can cause issues depending on the environment, you can simply download the module and adjust it to your own needs. After adjustments, upload it again and reapply it with another configuration version as described above.

💡 STIG implementation: The simple way

Applying STIGs in only a few steps simplifies the deployment of secure systems without the need for complex infrastructures or procedures. With XOAP, you have one central console to configure the security configurations, check the compliance state of your connected nodes and to deploy further updates when needed.

As we regularly provide new STIG DSC modules on GitHub, you can always upload the latest available ones to your workspace and use the same procedure as described above to apply the newest STIG security settings.

If you need additional help getting started with applying STIG book a free 30-min demo. 👋

Apply STIG security standards for free

The post Apply STIG security compliance in a few steps appeared first on XOAP.

]]>