Search
61 results for “nolabnoparty”
-
[ Blog ] Veeam v12.3.2.4165 #patch
Veeam has released a new Veeam v12.3.2.4165 patch to resolve some security vulnerabilities.
Installing this patch is strongly recommended to mitigate potential critical security risks.
Resolved vulnerabilities
This patch addresses the following vulnerabilities:CVE-2025-48982 - Severity: High | CVSS v3.1 http://rviv.ly/1VBD34 #CVE #CVE #CVE #vulnerabilities
-
[ Blog ] How to #backup #Microsoft Entra ID with Veeam
With latest versions of Veeam Backup & Replication it is possible to backup Microsoft Entra ID to enhance the protection of cloud services used by your Organization.
Microsoft Entra ID (formerly #Azure Active Directory) is Microsoft's cloud-based identity and access management service. It helps organizations manage user http://rviv.ly/qDANYE #entraid
-
[ Blog ] Proxmox VE 8 to 9 upgrade guide
The release of version 9, introduces new features and significant improvements making the #Proxmox VE 8 to 9 upgrade worthwhile.
By upgrading, you gain access to the latest features, critical security patches, and performance optimizations.
Prerequisites for Proxmox VE 8 to 9 upgrade
Before proceeding with http://rviv.ly/EvMkWF #debian #repository #aggiornamento -
[ Blog ] Veeam Backup for Microsoft 365 8.1.2.180 released
Veeam released the new Veeam Backup for Microsoft 365 8.1.2.180 version with some enhancements and resolved issues.
After installing this release, the new build number will be 8.1.2.180.
Enhancements in Veeam Backup for Microsoft 365Faster SharePoint and OneDrive backups - optimized how throttled requests are handled: http://rviv.ly/3WPMfX
-
[ Blog ] Proxmox #Backup #Server with NFS repository configuration
The #Proxmox Backup Server (PBS) is the Proxmox native solution designed to protect your workloads in case of failures.
Similar to the Proxmox hypervisor, PBS is an open-source solution that doesn't require any license to operate.
Install Proxmox Backup Server
Obtain the Proxmox Backup Server ISO from the http://rviv.ly/Fdy2Hc -
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] How to properly #boot a migrated Windows vSphere VM in #Proxmox
To properly boot a migrated Windows vSphere VM in Proxmox during a migration, you must follow a specific procedure.
Windows VMs are quite sensitive to virtual platform changes. This is because the storage #controller configured in the source environment often causes issues, the mismatch between the original controller http://rviv.ly/vOiGHj
-
[ Blog ] Omnissa #Horizon enable #copy and #paste from #Published Apps
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work.
By default, this feature is disabled for security reasons. A straightforward way to enable this is by using Dynamic Environment Management (DEM), a tool included with the Horizon solution.
-
[ Blog ] Monitoring #Proxmox with #InfluxDB and #Grafana
Monitoring Proxmox environment is an essential administrative practice for maintaining a healthy and fully functional system.
It allows administrators to proactively identify and fix issues before they lead to service disruptions.
This guide uses an Ubuntu Linux machine to set up the monitoring stack.
Install InfluxDB
The first http://rviv.ly/k0M4YA -
[ Blog ] Omnissa #Horizon 2503 upgrade guide: #DEM and Templates - pt.4
When installed in your Omnissa Horizon infrastructure, Dynamic Environment Manager (DEM) should be upgraded last in your component upgrade sequence.
You need also to update the associated Group Policy ADMX templates in Active Directory as part of the DEM upgrade process.
Blog series http://rviv.ly/lOZiwC #aggiornamento #vdi -
[ Blog ] Optimizing #Persistent #VDI with App Volumes and #FSLogix
When using #Omnissa Horizon Instant Clones, it's often necessary to have a persistent VDI to save user data and settings between sessions, as the clones are non-persistent by default.
To create this persistent area, you can choose between two main solutions:
Omnissa App Volumes
FSLogixIn a VDI http://rviv.ly/THU8Yj #appvolumes
-
[ Blog ] Proxmox #node replacement in #Ceph cluster
If a core Proxmox server fails taking its Ceph OSDs with it, the Proxmox node replacement doesn't have to be a nightmare.
To fix this issue you must cleanly decommission the failed server and correctly perform the Proxmox node replacement to ensure your Ceph data remains resilient.
The Ceph cluster should have the status http://rviv.ly/hDkYPo #replace
-
[ Blog ] Omnissa #Horizon enable #copy and #paste from #Published Apps
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work.
By default, this feature is disabled for security reasons. A straightforward way to enable this is by using Dynamic Environment Management (DEM), a tool included with the Horizon solution.
-
[ Blog ] Monitoring #Proxmox with #InfluxDB and #Grafana
Monitoring Proxmox environment is an essential administrative practice for maintaining a healthy and fully functional system.
It allows administrators to proactively identify and fix issues before they lead to service disruptions.
This guide uses an Ubuntu Linux machine to set up the monitoring stack.
Install InfluxDB
The first http://rviv.ly/k0M4YA -
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Optimizing #Persistent #VDI with App Volumes and #FSLogix
When using #Omnissa Horizon Instant Clones, it's often necessary to have a persistent VDI to save user data and settings between sessions, as the clones are non-persistent by default.
To create this persistent area, you can choose between two main solutions:
Omnissa App Volumes
FSLogixIn a VDI http://rviv.ly/THU8Yj #appvolumes
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: #DEM and Templates - pt.4
When installed in your Omnissa Horizon infrastructure, Dynamic Environment Manager (DEM) should be upgraded last in your component upgrade sequence.
You need also to update the associated Group Policy ADMX templates in Active Directory as part of the DEM upgrade process.
Blog series http://rviv.ly/lOZiwC #aggiornamento #vdi -
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Omnissa #Horizon enable #copy and #paste from #Published Apps
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work.
By default, this feature is disabled for security reasons. A straightforward way to enable this is by using Dynamic Environment Management (DEM), a tool included with the Horizon solution.
-
[ Blog ] Optimizing #Persistent #VDI with App Volumes and #FSLogix
When using #Omnissa Horizon Instant Clones, it's often necessary to have a persistent VDI to save user data and settings between sessions, as the clones are non-persistent by default.
To create this persistent area, you can choose between two main solutions:
Omnissa App Volumes
FSLogixIn a VDI http://rviv.ly/THU8Yj #appvolumes
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: #DEM and Templates - pt.4
When installed in your Omnissa Horizon infrastructure, Dynamic Environment Manager (DEM) should be upgraded last in your component upgrade sequence.
You need also to update the associated Group Policy ADMX templates in Active Directory as part of the DEM upgrade process.
Blog series http://rviv.ly/lOZiwC #aggiornamento #vdi -
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Omnissa #Horizon enable #copy and #paste from #Published Apps
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work.
By default, this feature is disabled for security reasons. A straightforward way to enable this is by using Dynamic Environment Management (DEM), a tool included with the Horizon solution.
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: #DEM and Templates - pt.4
When installed in your Omnissa Horizon infrastructure, Dynamic Environment Manager (DEM) should be upgraded last in your component upgrade sequence.
You need also to update the associated Group Policy ADMX templates in Active Directory as part of the DEM upgrade process.
Blog series http://rviv.ly/lOZiwC #aggiornamento #vdi -
[ Blog ] Optimizing #Persistent #VDI with App Volumes and #FSLogix
When using #Omnissa Horizon Instant Clones, it's often necessary to have a persistent VDI to save user data and settings between sessions, as the clones are non-persistent by default.
To create this persistent area, you can choose between two main solutions:
Omnissa App Volumes
FSLogixIn a VDI http://rviv.ly/THU8Yj #appvolumes
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Omnissa #Horizon 2503 upgrade guide: Connection Server - pt.2
The Omnissa Connection Server is the most critical component to upgrade, as any issues could significantly impact #VDI functionality.
This upgrade requires careful planning and after upgrading the App Volumes Manager, the Connection Server should be the next Horizon component in the upgrade sequence. http://rviv.ly/Zs70Bt #connectionserver
-
[ Blog ] Optimizing #Persistent #VDI with App Volumes and #FSLogix
When using #Omnissa Horizon Instant Clones, it's often necessary to have a persistent VDI to save user data and settings between sessions, as the clones are non-persistent by default.
To create this persistent area, you can choose between two main solutions:
Omnissa App Volumes
FSLogixIn a VDI http://rviv.ly/THU8Yj #appvolumes
-
[ Blog ] Omnissa #Horizon enable #copy and #paste from #Published Apps
When using Omnissa Horizon, the copy and paste operation between the local device and Published Applications may not work.
By default, this feature is disabled for security reasons. A straightforward way to enable this is by using Dynamic Environment Management (DEM), a tool included with the Horizon solution.