Delgado

Fair enough like. It's a bit daft that there are only two choices: 1) Obtain IP6 address (from where ?) 2) Set one.

Many thanks. Some solutions suggest changing the NLA service to a delayed start. But some still report issues. This looks a pretty solid fix: NLA uses dns to see what kind of network it is. If DNS is not fully functional at the time NLA starts, it cannot determine the domain existence. Simple fix: make nla dependant on DNS server start regedit navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NlaSvc Edit 'DependOnService Add new line with "DNS" I'm still not wild about how vague IP6 is defined for Windows server 2022. I'm willing to do some hex arithmetic if they are.

The simple stub zones on the other servers seemed to be working fine, when it's on the right IP address. I do miss the free use of profanity though and can only silently mouth the words in school. On the domains I'm trying to eventually migrate both the two 2012 domains to two separate 2022 server domains. Ideally with the minimum of disruption.

I haven't checked the event logs. I can see what has occurred when I check the adapter TCP/IP config. I made a reservation on the current DHCP server for it and it is fixed for IP4.

Thanks. I will be googling the meaning of that when back in. I should add that I left the IP6 setting as 'obtain'. I don't know if that is the correct setting - this will have to be the site DHCP server at some point.

I'm old school. I wouldn't know a VM if it bit me on my Harris. It's still a test server and not in production yet, though it is on the LAN with some client PC's. But obviously I want to move forward and put it into production if I can iron out the teething problems with it. Everything has gone swimmingly so far.

Environment is 2 windows 2012 servers (separate individual domain controllers) and this new 2022 server (in its own domain). It's a 2022 server standard edition (with desktop) build on a new Dell server. Fixed IP address. Server network defaults to Public network after reboot instead of Domain Network. This only happens occasionally after a reboot. The IP4 config defaults to a DHCP address! This throws out the stub forward zone records of two other domains on site. So my clients PC's can't get a login. For the test client PC's, which are in the 2022 domain, I'm having to work within the confines of the existing DHCP server leases from one of the 2012 site servers. So although the Clients can resolve the domain controller via the stub zone records of the other servers - it's frustrating when it happens. It's not a consistent error. Fixed by re-configuring a fixed IP again on the server. I wonder if it's related to IP6. Any suggestions most welcome. I'm on a long server migration strategy - to finally switch off one of the 2012 servers.

Google Sites - hands down the best.

Wordpress sucks so bad it blows. It is the most insecure web platform on the planet. So easily hacked. Practically a full time job to keep it patched. Rarely looks consistent on phone, tablet and PC. I've seen a local academy school using a Google site recently. Very tidy and very secure. They must be paying all of £20 a year for the domain name. Custom CMS sites - dear me - talk about money for old rope.

On curriculum PC's - one generic local profile for students, one for staff. All Internet history. login credentials and favourites deleted at logoff. UNC drives (including home drive) to Linux samba shares in Explorer. So that's like two.

Can I ask what version of Linux you used for AD? i've been looking at Ubuntu 22.04, The documentation online seems pretty scant. But it's been certified for quite a few new Dell servers.

I've used Workspace before and liked it. But I don't know how that tech works in internet outages on a LAN if your relying on cloud virtual servers for your data.

Two sites. < 100 PC's in total.

Hey thanks for the tips. I've looked at AD on Linux and it looks OK. I'm planning to use direct TCP/IP printing rather than server print queues. I'll probably run DHCP. But without AD I don't need LAN based DNS. Our ISP nameserver resolves internet name space for both the Linux box and the Windows clients. The Linux box and printers are just IP addresses. So everything is very quick like that.

Thank you for your post. Sounds like a good decision moving to pure Google for your school. Especially for the licensing simplicity.