Jump to content

mw184

Members
  • Posts

    304
  • Joined

  • Last visited

Reputation

14,027 Excellent

About mw184

Personal Information

  • Location
    North lincolnshire

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I managed to run a test this morning on multiple devices and the same problem still occurs. It boots into the LiteTouch but then doesn't even attempt to run the task sequence and just brings up the cmd box. Now extra confused as it is all as it was setup by the company in August and it still doesn't work. And to top it off when we contacted them for support, all they did was say it should be working instead of looking into it....
  2. So what I have done is removed the drivers I added to MDT and reverted MDT to the state it was before the issues started. I have regenerated the boot image and will give this a test when I get a chance.
  3. That's the strange thing, no devices can boot to the TS, even devices that have been imaged via the same TS previously.
  4. Only just got around to investigating this more, so sorry for the late reply to your message! I ended up building the devices manually. It took a bit longer but the devices just needed to be deployed to staff so it had to be done somehow. I am now back to looking into the problem. I have checked the network adapter on the server and it seems to be all ok, everything working how it should, but the same problem still seems to persist.
  5. So... for once there seems to be a disturbance in the force... DNS is looking healthy and seems to be working properly... even the DNS event logs are clear with nothing showing up as an issue.... I am not saying it isn't DNS, but for once it doesn't look like it is...
  6. Right, time to go digging. Wish me luck, I will update when I have news... (should have suspected DNS from the start, it always seems to be DNS when something goes wrong)
  7. I have just tried that and replacing the wds boot image with the new one, but still same problem. Tbh I am starting to find issues with lots of things like this, as the company set it up their way and then left, using custom scripts they made etc but explained none of it to me. I miss my old network haha
  8. So it won't talk to the deployment share at all. "System error 67 has occurred" "The network name cannot be found" Ran an ipconfig and it came back blank...
  9. I will give this a go and let you know, currently don't have my office as it is being used for y6 mock sats so been kicked out for a while.
  10. So when I tried a list disk etc there were no disks found on the device. However after the MDT was terminated, the laptop and the test PC I have been running since the issue started both booted through to the OS already installed. Both machines are displaying the same behaviours with regards to MDT booting straight to cmd.
  11. Hi all, can anyone help with this problem? Bit of background, back to using MDT and WDS after many years of doing intune deployments due to the IT work over summer by an external company, so I am a bit (more like very) rusty with MDT and WDS. They setup the task sequences and the boot images etc and it worked fine. I got a new laptop delivered which is a make and model we have never used in school before. Put it through MDT to see if it would work and it gave me a script error but no details. Did some digging and found out about the win11 issues with MDT and WDS. Tried an older version of Windows 11 to see if that would deploy, same problem. I therefore returned the task sequence to its original state with the other version of windows set to deploy. I then remembered drivers etc and went and downloaded the drivers for the device and put them into MDT. I then (as many guides online said, as well as one of the guys at the tech company) regenerated the boot images via MDT and then replaced the image in WDS with the new boot image. I then set up a boot and as soon as MDT/WDS loaded on the client machine, no task sequence started, instead a cmd box came up and nothing further happens. I am looking into the Litetouch.vbs and also into the task sequence but am not quite sure what else to try. Does anyone have any ideas? Many thanks!
  12. Glad its not just me!!
  13. Thanks for all the replies so far. I have been looking into options and wanted to check a brand name. Has anyone had any experience with Optoma? I just stumbled across them on AVPartsMaster and the price looked amazing (almost too good to be true...). In the marketing material, it looks really really good but marketing material will always say that! Here is the link to the product if anyone is interested: https://avpartsmaster.co.uk/interactive-solutions/optoma-5752rk-75-4k-70001-interactive-touchscreen-display#product-tabbed-content-default_1721730875782
  14. We currently have a board starting to fail, and age wise others are not far behind it so I am starting to worry about a number of screens that will need replacing. We currently run mostly CleverTouch but have a couple of BenQ boards that have been really really solid. Does anyone have any recommendations for any good and affordable touchscreen boards etc? Open to all options, not bothered about it being a "popular brand" like Smart etc! Cheers!
  15. The other problem I can see coming from something like ink-to-text that they want through word is accuracy. If the exec head doesn't have great writing, or it is really scribbly and fast etc, ink-to-text is probably going to have a hard time actually converting it accurately. Especially if they are walking around holding the device in one hand, writing with the other. Personally my writing is terrible when sat down, when walking it is really really bad. I don't think it would have a chance of working accurately ever with me. So unless they have perfect handwriting, it isn't going to work well. I would maybe use that as an additional "consideration" to use if they ask you about it etc, kind of pushes it back on them to consider how well this would actually work for them.
×
×
  • Create New...