DJamesS

We're looking for some help with an issue with printing to a large Konica Minolta Bizhub please. The printer is installed on Windows 10 Pro and is fine for printing to, as a network printer (direct IP, not via a Print server). Within the Printer properties/settings, the option is enabled for pass code authentication. When the user prints, a small box pops up, the user enters their code, and the print is submitted to the printer and prints out. So far so good. The user then goes home, prints a variety of documents while at home, with the theory being that they will print out when the user joins the network. What actually happens however is that the job never appears in the local queue on the machine, and therefore isn't sitting there ready for when the user joins the network. The previous printer that the workgroup had didn't have the authentication, and therefore the jobs would simply sit there until the user joined the network. Just looking to see if anybody else has similar behaviour with a similar setup please? Thank you in advance

Evening, In general, the solution you're looking for should be achievable, to a point. Please can you post the models of HP switch that you're running, just to confirm that they are managed switches and are VLAN aware/configurable. AirServer will be a sticking point. Unfortunately it doesn't easily cross subnets/VLANs. There are solutions to make it possible, but it adds a layer of complexity. A possible solution would be to configure the switch ports that would be assigned to the Projector linked PCs, to be on the Staff Wireless VLAN/subnet (untagged). Ensure that the Staff subnet is routable with your default VLAN, assuming your servers live on the default VLAN and are accessed by the PCs. Staff/Class iPads (assuming they are not BYOD student iPads of course) could then send content to the Projector linked PCs. Student and Guest VLANs would be separate, and i assume certainly the guest VLAN/subnet would not be routable with the default or Staff VLAN/subnet. All of this is pretty top-level, so apologies for the lack of specifics. Happy to help further if you think this approach would cover your AirServer requirement.

Hi there. Just a couple of thoughts on this. When the shutdown occurs, is that a scheduled controlled shutdown of the VM with Papercut on it? I assume it is. It sounds as though the server perhaps hasn't successfully been through the shutdown. It is as though the server has started a shutdown process, hence RDP and Papercut services no longer respond as such. It is worth having a look through the System Event Log, particularly looking for USER32 events around midnight. Assuming such an event is present and details the shutdown, have a further look through for errors, and also the point at which the Event Log service is stopped. You might get a clear indication of whether the shutdown has occurred. Hope this gives you a lead on where the problem is. A further indication could be to setup a free edition of PRTG or Spiceworks Network Monitor, and get it to push out an email when contact with the server is lost (no response to Ping). That would confirm whether the server does fully shutdown too. Anyway, hope this helps or at least gives you some avenues to explore.

The approach to resolving the issue, transfer roles, demote server, promote server seems sensible. What i would add is, make sure you do a System State backup of both the troubled server and a 'known good' server. This give you an option to get back to a good copy of Directory Services if things don't go to plan. Before attempting to do anything with Directory Services, also ensure that your Domain Controllers have a 'known good' DNS server specified in the IPv4 settings. Before and after the work, dcdiag, repadmin /replsummary and repadmin /showrepl are great command for checking general DC health and importantly, how well the replication is working. Be interested to hear how you get on.

As pantscat says above, Exchange makes things a bit more of a pain. A fresh /new forest is definitely the way to go, much cleaner and less hassle. The big thing though is in the testing! Setup a couple of servers, on an isolated switch, setup Exchange with some test mailboxes, setup a server to represent what will be your new domain, and a new Exchange server, and test (and re-test) the mailbox migration. Might be worth checking the SQL setup for SIMS too, as that may well need re-permissioning. If SIMS is supported by a third party, definitely get them onboard (easier said than done, but easier to plan up front than fire fight if SIMS doesn't play nicely after the migration). The upheaval (if that is the right word) is worth it in the end, a new clean 'known quantity', without any left over policies, permissions, etc.

We have a variety of Unifi implementations across different types of sites. The posts above speak volumes on the number of clients that are being supported on Unifi systems. For the price, the features included are excellent, with multiple SSIDs and VLANs, bandwidth limiting, and guest access with redirection to a built in captive portal, and external captive portal if needed. Cloud based controller on AWS is also a great option if you have multiple sites and/or don't want to run a controller in house. Well worth getting your hands on even just a single unit to explore the features.