LabTech is now ConnectWise Automate®. Formerly known as LabTech, ConnectWise Automate is still the same powerful remote monitoring and management solution to help you eliminate technician inefficiencies, automate your IT services, and master proactive IT service delivery. Now simplifying our software under one company means you have one. Thank you for this quick reference. I have this bookmarked as its helped me resolve some unrelated issues with exchange. However, according to the Microsoft documentation for Set-POPSettings and Set-IMAPSettings, you dont need to assign the wildcard to the IMAP or POP services. You only need to assign the wildcard to the SMTP and IIS service.
Let’s Encrypt has just added support for wildcard certificates to its ACMEv2 production servers.
I couldn’t find a simple guide on how to use it to create wildcard certificates for my domains, but I figured it out, so here’s how I did it.
Use Certbot From Github
The packaged version of certbot doesn’t support wildcare domains yet, so we’ll need to install certbot from the github repo:
Configure a DNS Authenticator
Using wildcard certificates requires you to use DNS based authentication, which adds a custom TXT record to the DNS for the base domain you’re using to verify that you are in control of the domain you’re getting a certificate for.
You will need a DNS authenticator plugin for certbot. Several are available, but I’m going to use CloudFlare for this example.
Check to see which plugins are available for your certbot environment as follows.
The plugin isn’t installed yet, so we need to add it.
Adding the CloudFlare DNS Authenticator Plugin
Now we see the plugin is available for use:
Adding the Plugin With Pip
Alternately, you can install the plugin from published packages using pip.
Configuring Plugin API Credentials
To use the authenticator plugin with CloudFlare, you need to be able to authenticate to CloudFlare so it will let you edit the domain entries to add your TXT entry to verify you control the domain.
Because Let’s Encrypt means we can do automated certificate renewals, we have to let the computer make DNS edits automatically. This is slightly problematic, because it means you can’t use 2-factor authentication on this mechanism (or you’d have to wake up in the middle of the night to insert your Yubikey in a server in a datacentre on the other side of the world… somehow). You’ll need to obtain API credentials for your DNS provider, and then ensure these are kept very safe on the server doing the automated certificate renewals.
CloudFlare, for example, doesn’t let you lock down what the API access can be used for, or where the requests can come from. It’s an all-or-nothing proposition, which is not ideal, so be aware of the risks before you set this up.
You obtain the Global API key in CloudFlare from your user profile. It looks like this:
Put these keys into a configuration file. certbot uses a default directory of
/etc/letsencrypt
, so let’s create a file called /etc/letsencrypt/dnscloudflare.ini
to store these credentials. The format of the file is like this:Make sure the file is not world readable.
Certbot Configuration Settings
Wildcard certificates are only available via the v2 API, which isn’t baked into certbot yet, so we need to explicitly tell certbot where to find it using the
server
parameter. For this example, I’ll be using the staging API endpoint which is designed for testing. Change it to the production API when you’re satisfied everything else is set up correctly.Certbot uses the
/etc/letsencrypt/cli.ini
configuration file:Get a Wildcard Certificate
If we’ve configured everything correctly, certbot should now be able to automatically request a new wildcard certificate via the ACME v2 API and use the CloudFlare API to put the required TXT entry in the domain’s DNS records via the dns-cloudflare authentication plugin.
Now you can use wildcard certificates with your usual certificate installation method.
Enjoy!
Creating collection to get computers that starts and end with particular string is used mostly using % .If this percentile used at the end of the variable name, you get all computer names that starts from particular string and if you use this in the beginning, gets all computers that ends with particular string.
Examples : To get all computer names that starts with ESKONR, use ESKONR% , to get all computer name that ends with ESKONR ,use %ESKONR.
But what if need all computer name that has letters like ESK in the middle of the computer name. Let says i have computers with 15 digits and they have ES placed in 10-11 . Example : INHYD1202ES0003
We can use underscore as wildcard for one character space and use them along with Like statement and apply to fields.
Collection :
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,
SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Name like '__________ES___' and SMS_R_System.ResourceDomainORWorkgroup = 'ESKONR'
SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Name like '__________ES___' and SMS_R_System.ResourceDomainORWorkgroup = 'ESKONR'
We have used 9 underscores in our query before E and 4 Underscores after S to tell that first 9 digits can be any thing and last 4 digits can be anything .
Underscores (_) as wildcard can be used at any location in the query but one can replace one character only.
Hope it helps!