|
What silly procedures? KMS works with DNS SRV records, it should all just happen seamlessly unless someone's manually set KMS information on the machines.
|
#
?
Apr 12, 2018 15:44
|
|
|
|
| # ? Jun 11, 2024 12:25 |
|
|
Is anybody in the MS Teams Direct Routing preview? https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Direct-Routing-enables-new-enterprise-voice-options-in-Microsoft/ba-p/170450
|
|
#
?
Apr 12, 2018 15:55
|
|
|
KMS is super-fun when your Helpdesk lead has DA permissions and loads the KMS server key in to the workstation image so every time he images a new system it hijacks the DNS SRV records
|
|
#
?
Apr 12, 2018 16:00
|
|
|
Thanks Ants posted:Is anybody in the MS Teams Direct Routing preview? No, but if it’s as cool as it sounds I am seriously pushing for this when it hits GA.
|
|
#
?
Apr 12, 2018 17:03
|
|
|
Yeah I have a compatible SBC and a group of people who know how to use it ready to fulfil my requests to have Teams deployed using our existing trunks and in a way that keeps extension dialling working.
|
|
#
?
Apr 12, 2018 20:15
|
|
|
Internet Explorer posted:I feel like we've been over this. The customer explicitly told us they don't want biometrics on the workstations because they don't want to manage additional hardware. They already have our software and want to leverage that. This is being driven by their security guys and that's the solution they want.
|
|
#
?
Apr 12, 2018 20:35
|
|
|
KillHour posted:The customer explicitly told us they don't want biometrics on the workstations because they don't want to manage additional hardware. They already have our software and want to leverage that. This is being driven by their security guys and that's the solution they want. anthonypants posted:Better change your name to BillHour because you're gonna be busy
|
|
#
?
Apr 12, 2018 20:45
|
|
|
skipdogg posted:What silly procedures? KMS works with DNS SRV records, it should all just happen seamlessly unless someone's manually set KMS information on the machines. The silly procedures are the things I have to write to show the exact sequence of steps I am taking in setting up and testing the KMS service itself. Paperwork for the clients to show "yes we did things the right way", basically. Checking the status of activation before and after by using slmgr/ospp, etc.
|
|
#
?
Apr 12, 2018 23:17
|
|
|
Oh hell yes, the result of project Honolulu is out. Playing with this thing 5 minutes in and I already love it. https://docs.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/windows-admin-center
|
|
#
?
Apr 13, 2018 12:50
|
|
|
devmd01 posted:Oh hell yes, the result of project Honolulu is out. Playing with this thing 5 minutes in and I already love it. Unsupported Server Version Server connections are only supported for Windows Server 2012 and above Boo!
|
|
#
?
Apr 13, 2018 13:28
|
|
|
Also WMF 5.1, ugh. Time to get that deployed to all the 2012R2 servers!
|
|
#
?
Apr 13, 2018 13:33
|
|
|
devmd01 posted:Also WMF 5.1, ugh. Time to get that deployed to all the 2012R2 servers! I like how the error message is that the OS is unsupported and not that WMF 5.1 needs to be installed. By all means don't give me an accurate error message and god forbid direct me to the download or *gasp* download and install it for me. That's Microsoft!
|
|
#
?
Apr 13, 2018 14:41
|
|
|
Internet Explorer posted:I like how the error message is that the OS is unsupported and not that WMF 5.1 needs to be installed. By all means don't give me an accurate error message and god forbid direct me to the download or *gasp* download and install it for me. That's Microsoft! The Honolulu Team probably couldn't get a license from the WMF team to redistribute or auto-install the dependency.
|
|
#
?
Apr 13, 2018 15:57
|
|
|
Good thing they all now have Microsoft TEAMS to COLLABORATE!
|
|
#
?
Apr 13, 2018 16:12
|
|
|
GreenNight posted:Unsupported Server Version
|
|
#
?
Apr 13, 2018 18:20
|
|
|
It doesn't work with my Netware servers?!?!?!?
|
|
#
?
Apr 13, 2018 18:26
|
|
|
The display connected to my 2010 Mac mini is broken, will this let me manage my Open Directory?
|
|
#
?
Apr 13, 2018 19:15
|
|
|
I'm trying to set up PXE booting for both UEFI and legacy clients. I have WDS running on one server, and DHCP running on a separate server. Both servers are running Windows 2008r2, are on the same subnet and VLAN, and are even connected to the same switch. Through researching, I know that this is possible when using server 2012 DHCP server and policies, but DHCP policies don't seem to be available with 2008r2. I know that I could switch option 67 on my DHCP server to point to the appropriate bootfile, but since I regularly image both UEFI and legacy clients, that sounds like it's going to be a pain in the rear end switching back and forth all the time. So, is it possible to do this using server 2008r2? If yes, how? Thanks.
|
|
#
?
Apr 13, 2018 20:02
|
|
|
I think you need to do it with IP helpers rather than DHCP options
|
|
#
?
Apr 13, 2018 20:09
|
|
|
You can do it with DHCP options. We have a DHCP server based on ISC DHCP so I don't know exactly how to do it in Windows, but this should get you going: https://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/ Basically you scope the different boot files to different architectures so that the DHCP server only offers the UEFI boot info to UEFI clients and vice versa.
|
|
#
?
Apr 13, 2018 20:25
|
|
|
FISHMANPET posted:You can do it with DHCP options. We have a DHCP server based on ISC DHCP so I don't know exactly how to do it in Windows, but this should get you going: https://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/ That's what DHCP policies do in Server 2012+, which is not available in server 2008R2
|
|
#
?
Apr 13, 2018 20:26
|
|
|
Oh see there you go, works fine in Linux! Also 2008 is EOL in less than 2 years, time to migrate!
|
|
#
?
Apr 13, 2018 20:32
|
|
|
FISHMANPET posted:You can do it with DHCP options. We have a DHCP server based on ISC DHCP so I don't know exactly how to do it in Windows, but this should get you going: https://2pintsoftware.com/whitepaper-using-dhcp-uefi-bios-pxe-booting/ Thanks, I saw that link a couple days ago and was all hyped to try it and then found out that it's not possible with server 2008. Set up IP helpers pointing to my WDS server and gave it another shot. Legacy clients will PXE boot without any problems. UEFI clients contact the server and look like they start to boot up, but then they just hang at a light blue screen. It's not a BSOD blue screen, it's just colored light blue, no text. Client sits there for about a minute then shuts down. This happens with 3 different models of Dell laptops.
|
|
#
?
Apr 13, 2018 20:32
|
|
|
Mr. Clark2 posted:I'm trying to set up PXE booting for both UEFI and legacy clients. I have WDS running on one server, and DHCP running on a separate server. Both servers are running Windows 2008r2, are on the same subnet and VLAN, and are even connected to the same switch. Serious answer, use dhcpd. It's way better than the MS provided dhcp implementation. You can serve different responses based on the vendor-class-identifier that is passed. Or chainload iPXE and do more intelligent decision making off of what iPXE finds. I do this for flashing the firmware of some specialty hardware. Obviously I don't want to even try to flash the bios of something that isn't this speciality hardware, so it gets flagged off with a class match first. #class "bios-intel-thing" { # match if substring(option vendor-class-identifier, 0, 9) = "PXEClient" and option arch = 00:00 and not known; # filename "/pxelinux.0"; # vendor-option-space pxelinux; # option pxelinux.magic f1:00:74:7e; # option pxelinux.configfile "pxelinux.cfg/bios-intel-thing"; # option pxelinux.reboottime 5; #} https://www.syslinux.org/wiki/index.php?title=PXELINUX This has basically all information you need to learn how to pxe boot things with Linux
|
|
#
?
Apr 13, 2018 20:33
|
|
|
My guess is UEFI booting isn't working properly on your WDS server. Try to PXE boot a UEFI client connected to the same network as the WDS server, that way you can know for sure it's receiving the broadcasts properly and responses are making it through. If that doesn't work then you've got a WDS problem.
|
|
#
?
Apr 13, 2018 20:34
|
|
|
Methanar posted:Serious answer, use dhcpd. It's way better than the MS provided dhcp implementation. You can do vendor-class-identifier stuff with Windows DHCP and I'm pretty sure (I mostly deal with VDIs, been a while) you can use WDS/MDT to get more granular, similar to how you described iPXE.
|
|
#
?
Apr 13, 2018 20:45
|
|
|
Wireshark it as well to see where it's breaking
|
|
#
?
Apr 13, 2018 20:45
|
|
|
Thanks Ants posted:Wireshark it as well to see where it's breaking Get your loving voodoo out of here!
|
|
#
?
Apr 13, 2018 20:46
|
|
|
Internet Explorer posted:You can do vendor-class-identifier stuff with Windows DHCP and I'm pretty sure (I mostly deal with VDIs, been a while) you can use WDS/MDT to get more granular, similar to how you described iPXE. This is correct. The only rub with Windows DHCP is that PXE still isn't supported by MS for whatever reason even though they provide information on how to do it. They still try to steer you towards using IP helpers.
|
|
#
?
Apr 13, 2018 22:55
|
|
|
I've got 10 new machines that I need to get imaged ASAP so I set option 66 on the DHCP server to point to the WDS server and set option 67 to point to Boot\x86\wdsmgfw.efi thinking that this would force the machines to load the UEFI NBP. Tested and...same light blue screen, then nothing. Booted up an older BIOS machine and figured that it would fail since it would be getting the wrong NBP...and it PXE booted without problem. So, I've got something misconfigured somewhere but I'm not really sure where to look at this point. WDS, DHCP and clients are all on the same subnet/VLAN. Legacy clients will PXE boot all day, the problem is only with UEFI clients.
|
|
#
?
Apr 13, 2018 23:24
|
|
|
Mr. Clark2 posted:I've got 10 new machines that I need to get imaged ASAP so I set option 66 on the DHCP server to point to the WDS server and set option 67 to point to Boot\x86\wdsmgfw.efi thinking that this would force the machines to load the UEFI NBP. Tested and...same light blue screen, then nothing. Booted up an older BIOS machine and figured that it would fail since it would be getting the wrong NBP...and it PXE booted without problem. UEFI is poo poo is the problem.
|
|
#
?
Apr 13, 2018 23:31
|
|
|
Methanar posted:UEFI is poo poo is the problem. It's really not; making DHCP do the dirty work of forwarding PXE broadcast traffic (poorly) is. IP helpers are the way to do this. DHCP options can and are made to work, but it will never work as well, or as hands off, as a simple helper pointing towards the WDS box. It's literally a single line in a config. If you can get that setup your problem will vanish instantly.
|
|
#
?
Apr 14, 2018 00:22
|
|
|
Wrath of the Bitch King posted:It's really not; making DHCP do the dirty work of forwarding PXE broadcast traffic (poorly) is. My understanding-and I could be completely wrong here-is that IP helpers are only necessary if the client is on a different subnet or VLAN than the WDS server. In my environment, WDS, DHCP and the client are all on the same subnet and VLAN.
|
|
#
?
Apr 14, 2018 00:27
|
|
|
Mr. Clark2 posted:My understanding-and I could be completely wrong here-is that IP helpers are only necessary if the client is on a different subnet or VLAN than the WDS server. In my environment, WDS, DHCP and the client are all on the same subnet and VLAN. If that's the case you don't need options at all; having them enabled is likely what is loving your setup up. If client, DHCP, and WDS are all on the subnet then broadcast traffic (PXE/DHCP) will reach those servers without additional configuration. If that isn't working and you don't have some wacky WDS setup I'd uninstall and reinstall the role. I know for a fact you can setup a 2012 R2 server with the WDS role at default settings and as long as you have both an x64 and x86 boot image associated with it it will boot UEFI and BIOS without a hitch. Wrath of the Bitch King fucked around with this message at 00:33 on Apr 14, 2018 |
|
#
?
Apr 14, 2018 00:30
|
|
|
MS are really upping their documentation game (I guess until they decide to move things around again). I like the project management oriented stuff they have now for deploying their stuff, like https://docs.microsoft.com/en-us/MicrosoftTeams/1-envision-define-my-success-phone-system
|
|
#
?
Apr 14, 2018 00:32
|
|
|
Wrath of the Bitch King posted:If that's the case you don't need options at all; having them enabled is likely what is loving your setup up. It wasn't working even before I enabled the options. I only enabled the 66 and 67 options today, I'm going to disable them again. WDS and MDT are up to date and I installed the 1709 ADK and updated my deployment share and generated new boot images before embarking on this project.
|
|
#
?
Apr 14, 2018 00:33
|
|
|
It's been a while since I've messed with WDS. Do you have bootfiles defined for the various architectures in WDS itself? From memory, there are a bunch of fields where you define what bootfile to use for x86, x64, x86_x64, etc. Unfortunately I don't have one I can look at right now to be more clear.
|
|
#
?
Apr 14, 2018 00:37
|
|
|
Thanks Ants posted:MS are really upping their documentation game (I guess until they decide to move things around again). I like the project management oriented stuff they have now for deploying their stuff, like https://docs.microsoft.com/en-us/MicrosoftTeams/1-envision-define-my-success-phone-system
|
|
#
?
Apr 14, 2018 00:37
|
|
|
Thanks Ants posted:MS are really upping their documentation game (I guess until they decide to move things around again). I like the project management oriented stuff they have now for deploying their stuff, like https://docs.microsoft.com/en-us/MicrosoftTeams/1-envision-define-my-success-phone-system I haven't checked their Server 2016 documentation in a while, how's that now? Last time I looked, they had plenty of documentation on Storage Spaces for Server 2012 R2 but zero for 2016.
|
|
#
?
Apr 14, 2018 22:07
|
|
|
|
| # ? Jun 11, 2024 12:25 |
|
|
Ok a few notes in no particular order 1) As others have said, don't mix DHCP options and IP Helpers. Either use one or the other, you can't mix them 2) Are you doing pure WDS or trying to boot SCCM boot images? 3) You say you're using the x86 filename, are you booting 32 bit UEFI devices? (you're probably not).
|
|
#
?
Apr 15, 2018 01:32
|
|