Forum Replies Created
-
Posts
-
Quick update on this. After a call with Dell support I was informed that this is a bug on the image. Dell said they had another client that when they set their time to Central Time they time was off by 2 hours. What they told me was to run a batch file to run tzutil and set it to Pacific Stardard Time. I had to run this on all my devices. Apparently the client had to run the same command but set the time to CST. I was told that Dell was going to fix this in their next Image release.
Ok, but what is the worst-case scenario if just reinstall WMS and reinstall WMS. Will the devices that are registered to WMS just will not show up on the console. Will I just have to go to each device, unregister the device and have it check back in to the WMS server?
CG I was able to resolve the issue. The problem I was facing is that someone configured a local GPO to hard code the home page and the WMS policy that I was attempting to apply was not allowed due to the Local GPO being configured.
Can someone tell me what is the process you guys take to prepar to pull an image. I know that I should be running sysprep for Windows 1o IoT, but when I push the image when the device boots up I’m asked to select the language, time zone, and keyboard layout. Later I’m asked to create a local account to get thru the intial setup. The admin and user accounts that come with the device originally image shipped by Dell is still there which is fine for me. But I think to go thru the initial process to set up every device and then to delete the account that I created is a lot of extra work. All I need is to have the admin and user account and configure auto login to the user account. I am not joining the device to the domain.
I believe that is the only option that I see as well. Unfortunately, I don’t use that option so I’m not familiar with it. I’m glad that you are a step closer to accomplishing what you need.
So sysprep has to be run wheter it’s joined to the domain or not joined to the domain? So then when I send the pull command from WMS, I will have to select sysprep then pull? I did try to do a sysprep and then pull, but then device booted up I’m prompted to configure a user for the device and the devices comes up as a brand new device, seem like there must be a way to bypass all that.
In the broke section, I only entered the FQDN of the storefront server without the store at the end of the URL.
Also, do not enter anything on the Citrix custom store name.
Give that a try and post your results.
I had the same issue so I imported my CA certificate into the File repository of the WMS server then on the Thin OS Device configuration under the security settings configuration look for Certificates and select the CA certificate by placing a check mark.
Reboot your device and give it a go.
Hope this helps.
El producto,
Thank you for your response. Yes, all the clients are already registered with WDM so I guess like you suggested I can sunset the DHCP options and setup WSM SRV record.
I was under the impression that if I removed the DHCP options the registered devices will no longer have the server they will need to check with, but I looks like once they registered with the server the agent retains that information. I was concerned that removing the DHCP options will prevent the existing devices from checking in.
Also I’m working on creating a new image with the latest WDA for devices that need to be redeployed.
Sounds like I should remove the DHCP options and implement WMS SRV record.
Thank You GC. We only have 30 devices on this server and we decided to play it safe and just deploy a new server with a brand new IP. If I deploy a new server with a new IP address can I just change the DCHP options and have the devices check in with the new server?
