User Profile
Ted_Mittelstaedt
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: DNS Issue
Because the Windows client resolver does not work this way. When you hand out IPv4 DNS server IP addresses, several hard-coded assumptions are made by Windows: The first DNS server in the list is ALWAYS going to be used unless it's offline. All DNS servers in the list are Microsoft Domain Controllers because the Windows client is supposed to be able to get replies to proprietary Microsoft DNS query extensions. For example, IETF does not define a record for "give me IP address of a Domain Controller for the domain I'm a member of" while Microsoft does. The first DNS server on the list has sufficient power/memory/CPU resources to respond to ALL DNS queries it might get from ALL clients on the network if the queries come in at the same time. For example, suppose a power failure takes down the ethernet switch infrastructure. On power-up, all clients will appear on the network at the same time, all will start querying for the IP's of the DC's at the same time, all will start querying for DHCP requests at the same time, etc. Once the server has booted, it's going to be inundated with these requests, and it BETTER have enough power to respond to all of them in a timely manner. Because of this there's certain items of "good Microsoft Networking practice" that should be followed: Do not setup a domain controller to do anything other than act as a domain controller/DHCP server Do break larger networks into subnets. A rule of thumb I have used is once you get over 100 devices on the network, start thinking about subnetting. Start by moving self-contained mobile devices like phones and tablets to their own subnet, if you have multiple sites subnet those, if you have a large site subnet by floors, etc. For supra-large enterprises you may end up going to 500-1000 devices per subnet but you should definitely stick to classful addressing - move to 172.16.X and use 255.255.0.0 or move to 10.x.x.x and 255.0.0.0 etc. While everything is SUPPOSED to be classless these days, don't make the assumption it is. DO have multiple domain controllers one per subnet and have them act as DHCP servers for their subnet - unless you are subnetting by site and you have very small sites, then it's OK to centralize DHCP/DC/DNS functionality and use DHCP helper addresses. DON'T setup a DC as a virtual server. You are better off with a low-end, non-RAID card, mirrored drive HP Proliant Gen9 running for example Windows Server 2019, then a high end super large ram multiple CPU hypervisor server running a DC in a VM. Setup the DC to power back up on AC power applied, set it up with a UPS that will wake up and repower on power failure, cabled to the DC for graceful shutdown, with a set of mirrored drives, and let the network beat the heck out of it. I know a lot of people try to save money in server licenses by trying to combine functions, but you are just going to hurt yourself later on if you do this. Spend the extra money for another server license and be done with it. What catches people who want to have a "failover" at the client is Microsoft has never clearly defined exactly what constitutes an offline, non-functioning DNS server that will cause the Windows client to go to the next DNS server in the list. I've seen people experimenting in a lab to test this and figure it out, but in production what I've always seen is when the first DNS server in the list fails the clients take a big kick in the rear to switch over to the next one. That almost always results in hesitations and slowness to the user experience, users WILL complain about it. And, if the first DNS server fails because it's just giving empty query results - then you have a real problem. It just works better to build the network so that whatever the client gets for it's first DNS server are among the most highly reliable servers in your network. It becomes a huge mess to remove and decommission a DNS server in an Active Directory that outright fails, and cannot be demoted the normal way and remove all it's objects via the decommissioning process, so don't set yourself up for this kind of failure in the first place by trying to combine DC functions into a user fileserver.13Views0likes0CommentsRe: Bluetooth and Wireless display not working on Windows Server 2022
Sergej, I am not talking about instructions on how to USE Bluetooth_HID.zip. I'm talking about how you figured out what to pick and choose out of win10 to get BT support to work on Server in short how you created the Bluetooth_HID.zip file to begin with. That process might be useful in the future for some other thing MS "forgets" to add in a future server iteration. If you have instructions inside Bluetooth_HID.zip on how to create Bluetooth_HID.zip and where to get the tools you used to figure it out, then PM me Bluetooth_HID.zip and I'll post the instructions only. I'd rather YOU post the instructions but you haven't. Once more I'm not interested in how to USE Bluetooth_HID.zip as that's been quite sufficiently documented in this thread. I want to know you CREATED Bluetooth_HID.zip5.6KViews0likes5CommentsRe: Bluetooth and Wireless display not working on Windows Server 2022
Elden we know perfectly well why you did it, the server team was more interested in jamming yet more instrumentation into Windows Server to follow our every move and market it to the world for filthy lucre, you simply responded to all your marketing teams requirements first and ran out of time before release for the core functionality. My guess is Windows Server, like Windows 11, is so heavily instrumented that more CPU power now in the OS goes into analyzing what we are doing on the Internet so you can market it than actually processing applications. Note that I'm not letting Linux off the hook either, nor MacOS, as the most recent Ubuntu desktop is chock full of that garbage also. When you stuck Show Search Highlights into the most recent updates for windows 10 - you really jumped the shark for uselessness of added features. News and Interests was bad enough but you had a lot of nerve sticking advertising popups into the Search window in Search Highlights and it is NOT intuitive on how to turn it off. At least News and Interests was somewhat intuitive in how the off checkbox was placed. But Search Highlights? Completely and deliberately not intuitive clearly you don't want people turning off the spam. That was 16 minutes of my life wasted searching for how to turn that off that I'll never get back. Of course I know you won't forward THIS to your server team.5.3KViews0likes2CommentsRe: Any potential problems with mixed OS versions for Active Directory PDC?
Both Domain and Forest level are at 2008R2 on this domain. However they are still all using FSR for replication of SYSVOL so thank you for that tip. I will need to run a migration to DFSR first on the existing DCs since Server 2019 does not support FSR.19KViews1like6CommentsRe: Copia de Seguridad Windows Server 2016 - Espacio en Disco Insuficiente - Volumen Fantasma
That unknown volume looks like it's the disk name of the backup volume. Windows backup is supposed to be smart enough not to attempt to list it's own backup disks in it's backup set so this shouldn't be a problem. How big is your PHYSICAL c:/ disk? I realize you are only seeing 480GB on there but if your c:/ drive is 1TB and your backup media is also 1TB that isn't going to fly.1.6KViews0likes2CommentsRe: Bluetooth and Wireless display not working on Windows Server 2022
I don't see the point of being all mysterious about the contents of bt_win2022 nor of your instructions, Serge. This forum and the Internet in general is littered with people who have posted "I have instructions for doing this here" to various links that are dead. Windows Server 2022 is going to be End Of Lifed in late 2013 are you going to keep your email address, google drive and that file around until then? What if you get hit by a bus and your heirs wipe all your accounts? Please be responsible about this. For everyone else and for future readers there's nothing special about bt_win2022 it is just older drivers and registry entries lifted out of windows 10. If you are reading this 10 years from now and Serge has long since moved on, you can reconstruct the contents by doing the same thing he did which is by installing old copies of win10, and copying the stuff you need out of them. Of course, it would be NICE if Serge could post his instructions for actually finding and copying out of win10 all of this stuff since it would likely be applicable for other drivers than just BT but if he does not, there should be enough instructions for doing this already on the Internet you will have to piece together for yourself. Or, we might be lucky and Serve will indeed still be responding to PM's 9 years from the date of this post.5.8KViews0likes10CommentsRe: Migration to Active Directory
When I have done this in the past I have always sat down with each user, had them login on their workgroup profile, show me where they were secreting all their files, then copied all their files to the new server, then logged out and logged in as their domain userID and setup shortcuts and drive maps to their files then copied any specialty shortcuts from their old desktop profile to the new logged in one. I don't give them access to their old files on their local PCs. They only get access to their old files off server shares. I have told them "the new system doesn't support saving files locally" even though that is a lie. I don't delete their old profile because invariably I'll get a call a week later from some user who is hell-bent-convinced that some critical file of theirs was accidentally deleted when it was moved to the server. So I can have them logout, then login to their old workgroup profile and show me where the critical file is, then logout and log back in to their domain profile and show them were the file was moved to. Most users who are older have had at least 1 disk crash in their lives so are more than happy to comply once they understand the reasoning why we save everything to the server and become more comfortable with doing it. I don't even bother with roaming profiles or any of that to force the issue, education is generally enough. It also gives me a chance to ID where they are saving all their web browser shortcuts and explain how browser sync works. I've only had 1 user ever object to this, her thing was "I have HR files and it's safer for them to be on my workstation than the server" I didn't even bother arguing with her since she ended up retiring and the replacement that they hired for her understood the importance of saving everything on the server where it would be backed up.2.4KViews0likes1CommentAny potential problems with mixed OS versions for Active Directory PDC?
Hi All, Just wanted to get people's opinions on the following: I have a customer with multiple sites, and 3 domain controllers. They also have a Microsoft volume license account so licensing is not an issue here. (they are a medical facility and thus under charity pricing and if any of you have not had experience with that let's just say pricing is disgustingly cheap next to free basically. I'm only saying this to eliminate a bunch of chaff responses of variations of make sure you got licensing) Each DC is at a different location. They also have an exchange server on premise running Exchange 2016 on server 2016 (bare metal). All sites are tied together with private circuits. The 2 "secondary" DC's are running Server 2016. The "primary" DC (it has FMS roles etc.) on it is running Server 2008R2. The Active Directory domain and forest functional level are all at 2008R2 (or they still could be at level 2008 I'm not sure at the moment) The primary DC was also used as a fileserver and is running out of space. So my thought was to setup a new DC on Server 2019, (bare metal) migrate FSMO roles to it from the old primary, demote the old primary and then setup another new fileserver (hyperv) and move all the files and shares off the old DC then shut it down. A question was brought up, wouldn't it be better to setup the new DC with Server 2016 that way all of the DC's are the same OS version? The target server I'm going to use is a Proliant DL380 Gen6 which I already installed 2019 on (HP only "supports" up to server 2008R2 on these but we have Server 2019 running perfectly on several others) My feeling is if I'm going to put time into building a server to use 2019 that way we can get the longest amount of life out of the installation. Basically what it boils down to is Server 2022 is unable to run on any of the older CPUs so Proliants older than Gen10 are SOL - which is literally all of this customers servers - they range from Gen 6 to Gen 9) I know Exchange 2016 can't run cannot run with anything newer than an AD Domain Functional level of 2016 so I was planning on installing the Server 2019 DC at Functional Level 2008R2 and then raising it later to 2016 level but not to 2019 domain/functional level. Do you think I should just install Server 2016 on the new PDC? We already have a number of Server 2019 servers in the mix just not Server 2022 yet (and probably not any for a while)Re: Windows Server 2019 install product key not working
Cedric_Miheso You have a photograph of a "Windows Server Retail" box. Those are sold along with OEM hardware. For example you go to Dell and buy a server online and also purchase Windows Server with it - you get that box along with a key inside the box. However, that key will only work with that OEM installer. It will not work with a MOLP installer ISO or a generic Windows Server install ISO and it will not work on non-Dell hardware. IN ADDITION since that key is a "retail" key you will have to login to the Microsoft Store and register it which will then produce the actual Product Key. The "retail keys" look like Product Keys but they are not actual product keys. Generally, that retail key is a match to the email address used to buy the license. When you originally bought that server from Dell and bought the Windows Server license along with it, Dell sent your email address over to Microsoft and MS sits on it waiting for you to login to the Microsoft Store with that address and the retail key. This is why you never buy copies of Windows Server from local IT stores. You buy them off the online Microsoft Store or you buy them from a retailer who is registered with Microsoft to be able to sell Open License. (as I am) What USED to be the case around 10 years ago is when people bought "retail OEM" copies of Windows Server along with their Dell servers, they got an actual live product key that did not have a corresponding match inside the Microsoft Store. Since Dell is allowed to sell Windows Server at a TREMENDOUS discount, people buying those servers to use for Linux, etc. would think "Cool I can spend $200 on Windows Server from Dell then turn around and sell it for $600 and make $400!!" Microsoft setup the Microsoft Store and the email match to put a stop to that. While it is POSSIBLE for a retail store to sell "retail Windows" software copies that are NOT oem, they have a specific way they do it and they will provide instructions on how to register and activate. The cost for those is NOT discounted so in my view you are far better off just buying those off the Microsoft Store. Also the Retail key is generally under a scratch off. It is dangerous to post a retail key like you have done because an unscrupulous person can register it and steal your copy so don't do that in the future. The store should have explained all of this as well as explaining that you must also buy Client Access Licenses to make your installation legal for most setups. You will have to go back to the IT store in Kenya and get product key registration instructions to login to Microsoft and get the real product key. Otherwise get your money back. If they refuse then call Microsoft and explain the situation. If it's an OEM copy they broke off of a OEM server sale then they will be in hot water with Microsoft since what they did is a violation of the license agreement. If it is a retail server sale then Microsoft will also be highly interested that they sold a Retail Server without also selling Client Access licenses. Lastly, I will state the following: Only Open License server product keys may legally be moved from hardware to hardware. OEM keys are tied to the box they were bought with. Once that box dies of old age/bitrot/etc. the key may not be used on another piece of hardware. Retail Keys are also risky with licensing. In practice they can be moved from hardware to hardware - as long as you don't do it often - but you MAY NOT just activate them on some piece of hardware without wiping that hardware if you move the key. And Microsoft's licensing language is very murky. The main thrust from Microsoft is they do not want people selling old keys like they did in the olden days. MS is OK for example if you have a retail copy of Office on a PC and that PC dies and you buy a new one, with you replacing that PC and reloading the key. But they are not OK with you loading that key on a PC then handing a copy of that key to your wife/girlfriend/etc. for their PC. Or selling that key to someone else even if you wipe it. At least you bought it from a store. Most of these scams are perpetuated over Ebay and when the buyer finds all this out the seller has vanished.27KViews0likes0CommentsRe: Windows Server 2019 install product key not working
step 6 worked for me I am on build 17763.107 that was the ISO that I just downloaded a half hour ago from the volume license service center. I absolutely share 10000% the sentiments about Ubuntu and I use it whenever I can get a customer to use it. Windows Server had some promise with version 2008 R2 but it's gone downhill ever since - there's no new features other than the ability to backup GPT volumes with Windows Backup that are of any real interest to the SB crowd - and all of this activation stuff should have been worked out ages ago - in fact it WAS worked out ages ago! There's no excuse for new bugs in what should be the most rock solid part of any commercial software that is involved in antipiracy copy protection of this nature. Microsoft would do well to recall that an entire company - Copy II PC - later PC Tools, - later Symantec - was founded on problems with ill-conceived software "protection"41KViews0likes0Comments
Recent Blog Articles
No content to show