serverfault.com

We are currently in the process of listing our hybrid SaaS solution on the Azure Marketplace as a transactable offer and would like clarification on the path toward MACC eligibility. Our understanding of the progression is: Publish SaaS offer on Azure Marketplace Achieve Co-sell Ready status Qualify for Azure IP Co-sell eligibility Become eligible for MACC-aligned deals We have a few specific questions regarding hybrid SaaS scenarios: Reference Architecture Diagram (RAD) Requirements For Azure IP Co-sell eligibility, we understand that a Reference Architecture Diagram demonstrating Azure service utilization is required. In our case, the product is a hybrid SaaS solution with limited direct Azure workload hosting. Most of our Azure interaction is through: Azure APIs / integration endpoints Azure Marketplace SaaS fulfillment A

After updating one or more packages with dnf, I usually use the needs-restarting command to find out if the server needs a reboot, but when the dnf update command finishes, the update has already been done and I have to reboot. What I'd like to do is know before installing a package if that update will require a reboot. The reason is simple: to keep the system updated automatically and postpone updates that require a reboot until a later manual intervention. I'd need something like: [user@host ~]# needs-a-reboot-after <PackageName> [enter] If you install/update "<PackageName>", you'll need to reboot the server. [user@host ~]# Is there already something out there that does this? Thanks everyone...

I've now got my Ceph cluster almost ready to use, but in the web dashboard, I don't see any of the four OSDs I've created. Neither do I find any of my NVMe drives the OSDs reside on: Error message: No devices (HDD, SSD or NVME) were found. Creation of OSDs will remain disabled until devices are added. Here is what I get on the command line: mixtile@blade3n1:~$ sudo ceph osd tree [sudo] password for mixtile: ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF -1 29.80798 root default -9 7.45200 host blade3n1 3 ssd 7.45200 osd.3 up 1.00000 1.00000 -7 7.45200 host blade3n2 2 ssd 7.45200 osd.2 up 1.

My setup: /etc/ns-shared-resolv.conf is written to regularly with nameserver x.x.x.x, updated from a script /etc/netns/ag2/resolv.conf is a symlink to the above (along with ag3, ag4).. for central DNS settings in root netnso Long-running service running in ag2 netns (via ip netns exec ag2 ..., launched from a systemd service) What happens: Everything works fine.. for some arbitrary number of hours. After that, DNS requests fail. Using tcpdump I can see DNS requests going to "the wrong place" .. the DNS server in root /etc/resolv.conf, NOT the netns one. At the same time while that's not working, ip netns exec ag2 cat /etc/resolv.conf works to show the correct settings. If I start a new ip netns exec ag2 bash shell, it gets the "corre

I am about to setup the licensing for the Remote Desktop server and point it to the licensing server. Problem is, I am not sure if this environment even has a connection broker server installed or do I need to install this on the RD host itself There will only be 1 RD host and this is replacing one that has been decommissioned. Is there a way to find out if this environment has this server from within the DC itself? update: sorry - totally forgot -Windows 2012 R2

I've got a Cisco Catalyst 2960 that I'm trying to configure for a remote office with 802.1X wired authentication. The setup I'm going for is Switch -> VoIP Phone via Internal Switch -> PC/Laptop (Domain Joined Win 7/8). Our authentication server is NPS on Windows Server 2008 R2. We are using Snom 300 handsets which do support 802.1X but it's not really feasible for us to configure it on all the handsets, so I've configured the switch to use MAB (MAC Authentication Bypass) for the phones. This for the most part is working brilliantly, the handsets get authenticated and put into the VOICE domain and the VLAN policy is displaying 501, which is our voice VLAN. But, the phones can still fully access the data VLAN - what am I doing wrong? Here is the 802.1x session into for that connected port: int-remote-sw-1#show auth sessions int Fa0/9 Interface: FastEthernet0/9 M

I'm looking to use my linux workstation on our company network, but i've been running into a few issues, specifically 802.1x i believe. I'm root on my machine and a windows domain admin so i should be able to access whatever i need to for this to work. Currently my linux machine has restricted connectivity which leads me to believe it's been put into a default vlan for non 802.1x clients. I guess my overall question is: How can i make my linux machine use 802.1x on the wired windows network ? The network is a typical windows domain and uses machine accounts as well as user ones. This is what i know & have tried so far: I believe i'm going to need to obtain a valid client machine certificate for the machine, the CA cert for the domain, and the private key for the client Idea 1, grab a valid key off a windows machine / domain ca machine I ran a windows VM upon the linux machine, and joined that to the domain, thinking this would

So I have my Windows laptops using 802.1X for authentication to connect to my WPA2-Enterprise WiFi network. This works well except for one edge case. These laptops are Windows 7 Pro and Windows 8 Pro. As a background, I have only been able to get users to successfully log in to such a laptop if their profile already exists in some way on the laptop -- ie cached credentials are used for the login, which are then passed on to the 802.1X process for authorization to connect to the WiFi. I am now being shipped laptops without physical ethernet connectors, meaning that I can't have users log in for the first time when connected by a wire. And therefore I have a chicken-and-egg problem: there are no cached credentials; the laptop doesn't try to connect to the WiFi because there are no credentials to pass through the laptop can't authenticate the credentials because there is no network over which to perform the authentication

I have taken over a server setup (as part of my job) which is setup of the following: Server setup with Threat Management Gateway (serving as the firewall) - 192.168.1.1 Server with Domain Controller Role - 192.168.1.10 Server with Radius and NAP Roles - 192.168.1.22 I have looked at a few tutorial to setup a Wireless Network using the 802.1x authentication. When going through the process of setting up the Radius Client I need to provide an IP Address. Most (because I have not seen every single tutorial or help file) of the tutorials links this to a Cisco interface, but I do not and I am a bit stuck for what to put in there. Do I need to put in the IP of the Radius Server or put in the IP of the Domain Controller - since that is where the Active Directory lives? This as far as

I want to know how to share a network of WPA2 enterprise with EAP-TLS, authenticating users with a common certificate. They share the same certificate. I'm afraid they can monitor each other. Is that possible? In EAP-TLS, do clients encrypt their packets with their own certificates or other session keys or else? Actually, the packets in WPA2 are all encrypted, but how?