Managing Multiple K1000s
We are buying an additional K1. We want to stick with an 8 hour check-in since we have communicated to our users that is what they can expect. It's a long story, and I don't really want to get into the details on that. I'm stuck with eight hours.
So we have about 6,000 machines that we patch, and push MIs. We have about 12,000 that have the agent just for inventory purposes, and the occasional install from the user portal. All of these rely on the eight hour check-in, so ORGs are out of the question. So our plan is to get this additional K1. We will have one that will manage those 6,000 machines, and another that will manage those 12,000. This way we can still maintain the eight hours without overloading the K1.
My problem is are users are used to going to a specific URL to get their software (user portal). I do not want to let our users know if you are on one of these 6,000 then you go here. If you are on one of these 12,000 then you go here. I thought about leaving the URL the same for the 12,000. For the 6,000 I've looked at modifying the hosts file to point to the new server even though they are entering the exisiting URL. In testing this has worked when pointing to my virtual K1. The only problem I can see that I cannot test at the moment is if there will be an issue with SSL since I do not have that enabled on my VM.
I know this is a really off the wall setup, and I do not think there's a lot of info out there for it? Does anyone have any better ideas on how to accomplish this?