Interested in learing how to let your external partner and users access your environment with their own credentials while still maintaining your wanted security. Want the users to be able to SSO from their own credentials into your environment? Then you will be interested in this post going through Entra ID b2b mixed with Citrix.
This writeup will show you how to hack the windows kiosk mode so you can use one config to target a multitude of devices requiring their own unique url. Unique kiosk device URL’s normally means unique configuration profiles in intune – or does it?
This post will show you how to set up your environment to support AzureAD joined devices authenticating with your on-prem resources. When devices are setup as pure azure ad joined, and not hybrid joined, devices we need to handle authentication to your on-prem resources in a better way. Your on-prem resources does not in itself understand the authentication from these devices. It will also add support for using Windows Hello for Business/biometrics, FIDO security keys
This post revolves around the e-mail concepts for SPF/DKIM and DMARC to increase your e-mail reputation as well as protecting your domain from being misused by others i.e impersonation. We will also go through the tool provided by Valimail to have this monitored, all integrated with your Azure AD for SSO.
LAPS – Local Admin Password Solution, has for a long time been one of those great tools to have in the toolbox when it comes to securing your devices from lateral movement from a potential attacker. And Microsoft LAPS have been around for quite some time already.
This tool was orginally available for deployment to server/desktop devices connected to a traditional domain (on-prem) setup.
This changed as of April 2023, and Microsoft have now introduced Microsoft LAPS (Preview) with support for configuration with Intune, and saving the passwords to Azure AD, giving us – once again – a native LAPS solution to handle the local admin account.
Recently I was troubleshooting terrible application Performance for a windows application.
This application is using files and directories located on a file server.
The file server OS was Windows server 2016 and the clients are Windows Server 2019 Citrix terminal servers.
The application uses seperate client folders containing files pr client, with alot of files inside the various folders – some more than others.
In this specific there were tens of thousands of files in some client folders.
Performance on the application was intermittently slow, and it could take upto 15 minutes to switch between one client and another inside the application Read on to get the solution
It’s no secret that Microsoft is doing good when it comes to their subscription-based Office […]
First of, what is Citrix SD-WAN? The short answer, it’s virtualization of your current WAN […]
Recently I upgraded Citrix Workspace Environment Management from v4.2 > 4.7. The environment for this […]
Using GPO’s to apply settings to users and computers have always been a great way […]