Sheridan

It fails right at the end, but only when using the 64 bit boot image. Now deployed several using the 32 bit version. Bizarre but I'll have a look when I've got more time. Both the boot images were rebuilt (several times!) so they're both the same date.

I'm using the adk for 1607 and the latest MDT Update 2 and updated the deployment share from scratch - however I've discovered it works if you use the 32 bit lite touch boot image, but always fails with the 64 bit image!? At least I can work with that - not sure why there is a 32 and 64 bit boot image anyway as its just a bootstrap image anyway.

We have a freshly captured 1607 image with all our apps etc on, on our WDS/MDT server. When we deploy this to any machine, it goes through the deployment stages (very little changes made to the deployment task for this test) and it fails every single time with the error: I'm struggling to find what this is doing, it pretty much drops the image on and then fails. Is MDT 2013 Update 2 even capable of deploying the 1607 update now?

Meh, a list of twiddles and tweaks. Nothing that is much practical use. I'm not obsessed with the control panel - I just think the whole thing is a half assed mixup. If you're going to give us a new 'immersive' control panel then flipping well get on and do it! And if you're giving us Edge to replace IE, then how about some useful GPOs, and if we have to have the clunky start tiles how about GPOs that work for those too! And for gods sake, get rid of that ridiculous 'Hi...We're just getting things ready for you' Argggh!!!!

Err installed 1607 and so far noticed no difference. Same old stuff and missing gpos. Control panel still a mixture of old and new. A year of testing and that's it?

I've now tried disk2vhd and starwind to convert it - and that vm just bsod's on boot. I've had to admit defeat on this one, now rebuilding a brand new vm and will have to try and restore a backup to it! A bit worrying as I've got quite a few physical servers to convert and this has taken a week of trying! Thanks for the suggestions and ideas though - all worth a try! Edit: Nope. This is one server that will have to remain physical - everything I try results in a blue screening vm! Even doing a full restore and backup using Windows Server Backup fails.

I've rebooted both the client and esx servers and to no avail. The common error that relates to 98% seems to only relate to Server 2003 and its boot.ini file. I'm looking at fresh install and restore from backup next!

The only error I can find in the log is two of these: That doesn't tell me much!

Cheers I might have a look at those next week.

I'd settle for that but when I try to connect it pops up a message saying port 7100 might be blocked, but this happens even when the Windows firewall is disabled.

I'm thinking about using something like reflect to create a new image and then try p2v on that, but I need to find a free version that will do it!

I give up - looks like this machine will be a physical server forever more! I've tried everything and its always the same meaningless error

Just a sata CD drive - and 2 sata drives (that were mirrored but aren't anymore!)

I've been converting some old physical servers to VMs (ESXI6) and have got stuck on one particular 2008 R2 server - its only has a few roles and only has 250GB of disk space! However it fails the conversion process every time, whether done locally or remotely - the error is pretty useless 'A general system error occurred: InternalError' and this happens at 98% every time. VMWare only seem to mention boot.ini files (for Server 2003) or missing driver files (which doesn't seem to apply in this case as the error is such a vague one!) This is a pretty standard HP Server running 2008 R2 with nothing odd about it - anyone seen an error like this before?

Looks like I'm going to have to give up with airplay in our setup. We have xirrus (cloud managed) so that might be a complication even though it has Bonjour Director enabled for all vlans. Our APs are all on one VLAN and the wired clients on various other VLANS, they all access the internet through a smoothwall, then firewall (which are both on the server VLAN) - presumably if I had a wireless controller onsite this would work as people with Ruckus ZoneDirectors have got this working - with the xirrus being cloud I don't know where the bonjour redirection is taking part?

What did you do to get it to work across vlans? I've got Xirrus setup to enable Bonjour Director across all VLANS, and multicast enabled across the wired/wireless vlans, yet the ipads cannot see the Airserver PCs?

Air server is great, but it doesn't work across vlans or different subnets. I've tried everything to get our xirrus wireless connected iPads to connect to air server but it's not happening!

Not sure what I did though! [emoji3]

We're trying to get airplay working on our wireless vlan - we've configured Bonjour director on our xirrus APs to forward traffic to all the vlans, and installed Airserver on the wired PCs in classrooms. Problem is, the ipads cannot see the PCs running Airserver - they're on seperate vlans of course but the xirrus APs are set to forward this. However when you try to use the Airserve Connect app on an ipad, you get an error on the airserve PC saying port 7100 might be blocked - even if the firewall is turned off completely! Am I missing some part of getting airplay to work across vlans? Our vlans are routed by the core switch and the devices on the wireless vlan have normal access to other network services.

Well this gets weirder. I restarted the NPS from home last night and when I tested a couple of laptops this morning they now connect to the new SSID without complaint - using the GPO that I was using yesterday. The restart must be a coincidence, as the W10/Ios clients were working on the new SSID without problems yesterday. I'll have to try a few more and see if it carries on working!

I'm a bit baffled as to why the Windows 10 and IOS devices seem happy to connect - they have the same certificates (ie the one given to the NPS server by the CA, and the root CA) and they work fine! I'm not sure where this is going wrong, the new part of this is the Xirrus part, but the 802.1x setup in there is simple and appears to work with other devices. Annoyingly the Windows 7 clients declare the CA is not a trusted anchor, yet it shows up on the Certificates MMC as a Trusted Root Authority, so that's conflicting information - especially as I've set the wireless policy to not check the server certificate.

No sccm here, it's frustrating as the new ssid is identical to the previous one except in name! I'm tempted to redeploy the old one to see what happens!

I'm going to try and create the profile manually tomorrow and see what happens. Whatever it means I've got to go around every laptop to fix them now [emoji15]

We've move from old ruckus kit to new xirrus and basically deployed a new ssid with the exact same security settings as the old ssid (we basically created a new ssid for clarity that we were using the new kit!) The old ssid and new connect to nps on server 2012 which again hasn't been changed. The GPO is a new GPO for this ssid, the old gpos have been removed. Oddly it will connect on Windows 10 and IOS with no warnings, but the Windows 7 won't connect without a warning, and that means the network isn't available on boot, rendering a load of laptops useless. I can't see it being a problem with the xirrus as that is simply pointing to the same NPs server as our old ruckus system did, and other clients seem OK and don't complain about the certificates. Very bizarre.

That's the odd thing, it's always been unchecked! It's only started complaining since we applied this policy to our new wireless system, which is the same as the old just using different APs.