MoPositive

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 28 total)
  • Author
    Posts
  • in reply to: New Wyse 5070 Pushed Image Dell Quick Start Loop #106997
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    I ran into this problem recently with a new 5070 image I created for our organization.  Some poking around showed there is something at startup that runs a batch file that checks for the presence of C:\Users\Public\Documents\Wyse\first_boot.txt and, if the file is present, launches the quick start page.  Used a command file in an app policy to delete this text file and the page no longer launches on startup.  For future images, I’ll make sure the file is deleted prior to sysprep.

    in reply to: Auto-move TCs to different WMS Server? #106030
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    If you’re using WES, let us know, I’m about to go through a similar exercise.

    in reply to: Using Groups in WMS #105866
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    That note is specific to the ‘unmanaged group’, the place all your devices will go when they don’t have group tokens assigned (defa-quarantine).  Interesting that you could create groups without a group token, didn’t know that was an option.  I guess maybe that would be valuable if you wanted to create a custom parent group to apply policy to a set of devices but also wanted to segment that device set for more granular policy.

    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    What does DELL support say about it?  The fact that you reimage a device and it still pulls down an out of date configuration suggests to me that you have a server-side issue.  It’s been a while since I poked around in the WMS database but I believe there is something akin to a message queue in there and maybe it has some old instructions stuck in there and is not clearing and accepting new commands.  If Change Group uses a separate queue for its operation, that could explain why you can do that but other instructions fail.  Would definitely recommend getting DELL to look at the WMS database or, if you have the time, getting familiar with it by picking a client and using its device ID to explore on your own.  The tables have pretty self-explanatory names so you may be able to identify the problem on your own.

    in reply to: DNS Srv record or DHCP tags #105864
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    I’m not familiar with your client device type but I would base my choice on the complexity of the environment.  I work in a company where there are far too many DHCP scopes to keep track of but I only have to worry about 3 DNS domains for SRV records.  That made the choice easy for me.  I might not even find out what IP ranges are in use for clients until they start reporting in so relying on DNS makes the management of clients a lot easier.

    in reply to: Wyse WIN 10 IOT Image Pull with WMS #51176
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    I was going to suggest that file, WES7_CustomSysprep4man.bat.  Still might be the right one but maybe there are other files that need to be configured for input to the process.

    You might be better served moving this discussion in the WES forum as it’s really not specific to WDM/WMS.

    When it shut down and then you turned it back on, did it make an attempt to upload an image or did it immediately boot to Windows?

    in reply to: Wyse 5070 WIN 10 IoT Updates from Wyse Site #51175
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    If you are building a new image, I wouldn’t bother using the security updates from DELL.  Just let Windows Update do its thing before you finish the image.  Also recommend taking steps to clean up the files post-update as it will save some image space.

    in reply to: WMS – Wyse location #51173
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    It’s an attribute you can populate on the client end and have it reflected in WMS.  We don’t use it today but one scenario I could see it being useful for is segregation of devices in a facility beyond what can be done by subnet.  If a local site admin has the ability to set the value when putting the device online, it could help with auto-assignment of group membership.

    in reply to: Wyse WIN 10 IOT Image Pull with WMS #51172
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    I don’t have experience doing this with WES7.  I would expect the experience to be similar and likely involves sysprep.  Is there a C:\Windows\Setup folder?  If so, what’s in it?

    in reply to: Wyse 5070 WIN 10 IoT MS Updates and Anti Virus #50864
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    @nivlacckw,

    If I understand correctly, you have Windows Update setup to automatically download updates but not install them.  You mention that you have the UWF exception for where the updates are stored but do you see any impact on the filter cache during the download process and, if yes, do you see the memory free up after the download completes?

    How do you manage the install of the updates, do you do it from WMS or is it managed locally at the site.  I’m very interested to hear any approach people are taking to keep the OS current.

    in reply to: WMS agent registration fail #50863
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    You can also delete devices from the devices tab, just filter on unregistered devices and select the one you want to delete, the option will be in the More Actions dropdown.

    in reply to: Win 10 (Wyse 5070) TC Not registering With WMS Via DNS #50862
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Agree with VNad, the issue is most likely that the DNS suffix handed out by the DHCP server is not the same as the domain where you set up the SRV records.  Run IPConfig on the thin client and note the Connection-specific DNS Suffix, does it match the domain where you set up the records?

    in reply to: Wyse WIN 10 IOT Image Pull with WMS #50665
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    Here’s the steps I just posted in the other thread.  For the image pull, yes, select Pull after Sysprep if you follow these steps.  Selecting that will turn off UWF and reboot the client.

    High-level description of how I prepare an image:

    1. Download latest base image from DELL.  Use the USB tool to put it on a stick and image a client.

    2. Install/Uninstall/Configure all the crap I need in the image.

    3. Strip out whatever I can to make the image as small as possible.

    4. Turn on the write filter so WDA fires up and connects to WMS.

    5. Schedule an image pull for the client.  When this kicks off, it will turn off UWF and reboot the client.  Log in as Admin

    6. Open C:\Program Files\Wyse\WDA\Config\CCMProtocolConfig.xml and strip out the MAC Address, Owner ID, Wyse ID, Authentication Code and Group Key.

    7. Run (as administrator) C:\Windows\Setup\BuildMaster.cmd.  Pick your image preferences and let it do it’s thing.  When it’s done, it will shut off.  Turn it back on and it will upload the image to the WMS repository.

    in reply to: Cannot Push or Pull Image from 5070 WIE10 #50664
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    High-level description of how I prepare an image:

    1. Download latest base image from DELL.  Use the USB tool to put it on a stick and image a client.

    2. Install/Uninstall/Configure all the crap I need in the image.

    3. Strip out whatever I can to make the image as small as possible.

    4. Turn on the write filter so WDA fires up and connects to WMS.

    5. Schedule an image pull for the client.  When this kicks off, it will turn off UWF and reboot the client.  Log in as Admin

    6. Open C:\Program Files\Wyse\WDA\Config\CCMProtocolConfig.xml and strip out the MAC Address, Owner ID, Wyse ID, Authentication Code and Group Key.

    7. Run (as administrator) C:\Windows\Setup\BuildMaster.cmd.  Pick your image preferences and let it do it’s thing.  When it’s done, it will shut off.  Turn it back on and it will upload the image to the WMS repository.

    in reply to: Wyse 5070 WIN 10 IoT MS Updates and Anti Virus #50526
    MoPositive
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    If you plan to use Windows Defender for antivirus, the device is already configured to allow the updates to apply without turning off the write filter.  However, there are times where the update download is large enough to fill the write filter up and reboot the machine, depending on how long the machine has been running.

    I wish it were easier to apply Windows updates to these devices.  I find that deploying cumulative updates takes so long for download and installation that it’s too difficult to do on a regular basis.  Have also had issues where the windows update required a reboot to finish installing so always build an extra reboot into your deployment package otherwise you may find your client trying to finish the install after the write filter has been re-enabled.

Viewing 15 posts - 1 through 15 (of 28 total)