persistent image causes the client to loop over and over - Wyse WSM - Wyse Software - Dell Community

persistent image causes the client to loop over and over

persistent image causes the client to loop over and over

This question is not answered

persistent image causes the client to loop over and over

we have a laptop image that we published out to a group of laptop with hard drives. The image is in persistent cached mode ( mobile hard drive). The issue we are facing is this:

when we turn on the PC and assign it to the persistent laptop group, the image starts transferring to the laptop, it then reboots, and starts the same process over again in a never ending loop. The user logs in and the dialogue window pops up "imaging the device again", then the system reboots, says finishing item 6 of 7, logs in and starts imaging all over again.

this is happening at multiple linked sites, any clue what could be causing this?

thanks,
Patrick

All Replies
  • this is a wsm 5.1 installation with an HQ server and several linked sites

  • This is from the admin log and states persistence not supported and running locally - NOT Started - standby mode.....

    2013-08-07 02:10:17,928 [INFO] main <org.quartz.core.QuartzScheduler::initialize,241 > Scheduler meta-data: Quartz Scheduler (v1.8.3) 'DeviceGroupCmdScheduler' with instanceId 'NON_CLUSTERED'
    Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
    NOT STARTED.
    Currently in standby mode.
    Number of jobs executed: 0
    Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads.
    Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered.

    2013-08-07 02:10:17,928 [INFO] main <org.quartz.impl.StdSchedulerFactory::instantiate, 1275> Quartz scheduler 'DeviceGroupCmdScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
    2013-08-07 02:10:17,928 [INFO] main <org.quartz.impl.StdSchedulerFactory::instantiate, 1279> Quartz scheduler version: 1.8.3
    2013-08-07 02:10:18,116 [INFO] main <org.quartz.core.QuartzScheduler::start,497> Scheduler DeviceGroupCmdScheduler_$_NON_CLUSTERED started.

  • This is from the client log


    08072013 [16:17:19:978] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:17:14 2013
    ; Total: 2030354432 bytes (1936 MB); Bad write checksum: 0

    08072013 [16:18:19:980] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:18:15 2013
    ; Total: 2031426560 bytes (1937 MB); Bad write checksum: 0

    08072013 [16:19:19:982] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:18:41 2013
    ; Total: 2031598592 bytes (1937 MB); Bad write checksum: 0

    08072013 [16:20:19:985] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:20:19 2013
    ; Total: 2032476160 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:21:19:987] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:20:34 2013
    ; Total: 2032550400 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:22:19:990] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:22:17 2013
    ; Total: 2032941056 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:23:19:993] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:22:45 2013
    ; Total: 2033007616 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:24:19:995] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:22:45 2013
    ; Total: 2033007616 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:25:19:997] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:22:45 2013
    ; Total: 2033007616 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:26:20:000] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:22:45 2013
    ; Total: 2033007616 bytes (1938 MB); Bad write checksum: 0

    08072013 [16:27:20:002] - disk 2: First RW: Tue Aug 06 08:16:29 2013
    ; Last RW: Wed Aug 07 16:26:45 2013
    ; Total: 2033165312 bytes (1938 MB); Bad write checksum: 0

  • Maybe this is procedural issue. Please make sure you read "Mobile Disconnected Mode" in the WSM 5 Sizing and Planning Guide and follow the example in "WSM5 - 8 - Mobile Disconnected Mode.docx" of WSM5-HowToseries.

    Follow these steps:
    1. Delete the client from the WSM Admin Console at Headquarters and any other site
    2. If there is a DNS Record called CDServer , make sure the entry points in the Linked Site only to the Linked Site Core Server but not to any other WSM Server outside this site
    3. Make sure the to-be-provisioned device is not provisioned or if it was before, use the G-Key to wipe the list of local cached Authentication Server information and discard the entire OS Image present on the hard disk
    4. register the to-be-provisioned device to the Linked Site WSM Admin Console and assign it to a Group which has Mobile Disconnected Mode enabled
    5. Power on the device and let it do a PXE boot, then start provisioning in the Linked Site.

  • I grabbed a laptop that had a previous image on it. Deleted it from WSM inventory and deleted the computer account from Active Directory, rebooted the PC. Then i checked wsm admin GUI, 

    the machine now has a new name and AD Account and I can login as the local admin. I assign to the laptop image and rebooted the PC, logged in as local admin and i don't see the provisioning starting. 

    i check the admin GUI and it shows the PC "status = N/A", but on the device tab it shows Provision Status: Provisioning In Progress (Round 1 of 2). Yet i still don't see the popup message on the PC stating its provisioning. 


    I think i will reboot all of the servers and try again. thanks - any other ideas on what may be causing this. Its a brand new install of WSM 5.1

  • >I grabbed a laptop that had a previous image on it. 
    please make sure you wipe everything from the device using the G-Key when it starts the local WSM Bootstrap

    >i don't see the provisioning starting. 
    Is the device set to mobile disconnected mode in the WSM Admin Console?
    If Force Provisioning is set to Disabled, then oyu need to kick it off by right clicking the WSM Virtual Disk Image utility in the system tray

    >Its a brand new install of WSM 5.1 
    Please go for WSM 6.0.0 as this is the most recent version!

    Is provisioning not at Headquarters but not in Linked Sites or nowhere?
    Have you tested it works with a Device Group at HQ with the Laptop Image assigned, Mobile Disconnected Mode enabled, Force Provisioning set to enabled?
    If this works, go ahead and make sure the Site template is complete (Server Group, Device Group, OS Image, Device Template) and the OS Image is Enabled in the Linked Site. Delete the Device at HQ, wipe everything from the device using G-Key and add it to the Device Group with Mobile Disconnected Mode in the Linked Site.

  • The image mode = shared (persistent)
    Yes, Connection Type = Mobile Disconnected

    force provisioning is enabled - should I see a status bar when the provisioning is underway?

  • Absolutely yes. When you logon you should see the process kicking off and you should see messages like in "WSM5 - 8 - Mobile Disconnected Mode.docx" of WSM5-HowTo series.
    Is the image domain joined, try to logon as Domain Admin and see if this makes a difference.

  • thank you for all your help - yes all is joined to AD domains. The developers are looking at my ticket. I will post what the next step is.