Posts Tagged ‘symantec-ghost’

How to check for “lost trust” issues on LRC PCs before classes

  1. We experience computers that fail allowing students to log in, thus disrupting face-to-face classes in the LRC.
    1. We have found no diagnostic tool working, other than attempting to log into the machine.
    2. Current workaround is manually removing and adding them back to the domain, when students experience login issues – which is time consuming, certainly too time-consuming during classes.
  2. Suggested workaround Checklist, to be run before any class in the LRC (check calendar):
    1. Student staff
      1. logs in on each individual computer and notes failures (
      2. this could be accelerated by using mstsc, especially with remote desktop connection manager and lrc.rdg) on the reception desk computers
      3. do we have automated (scriptable) login options?
    2. Coordinator
      1. from Deepfreeze-console, unfreezes computers in question
      2. from Symantec Ghost Console image
        1. puts computers in question into domain-issues folder
        2. runs tasks against this folder
          1. “remove from domain”
          2. “add to Domain&AD”
      3. from Deepfreeze-console, freezes computers in question

More ways of making minor changes to a domain-joined, deepfrozen computer lab image

  1. Re-imaging a domain-joined, deep-frozen Windows XP language lab using Symantec Ghost and Deepfreeze can be a drawn-out process.
  2. Minor fixes can be achieved by unfreezing and using a Symantec-Ghost file task and a script that loads  the default user registry hive – here is how:
  3. sTempHive = """HKEY_USERS\Test"""
    '//vista and up: sDefaultUserHive = """%USERPROFILE%\..\Default\NTUSER.DAT"""
    sDefaultUserHive = """%USERPROFILE%\..\Default User\NTUSER.DAT"""
    sSName = oUtility.ScriptName
    set oShell = WScript.CreateObject ("Wscript.Shell")
  4. and alters it before freezing the lab again. Here are some examples of such fixes:
    1. change the default keyboard (after users logs in):
      oLogging.CreateEntry sSName & ": Setting US-International as Default Keyboard Layout",LogTypeInfo
      RegPath = "HKEY_USERS\Test\Keyboard Layout\Substitutes\"
      oshell.RegWrite Regpath & "00000409", "00020409", "REG_SZ"
      If Err<>0 Then 
        oLogging.CreateEntry sSName & ": Failed to update Default Keyboard Layout setting",LogTypeError
        Exit Function
      End If
    2. change visibility of the developer tab in the ribbon of MS-Word:
      oLogging.CreateEntry sSName & ": Setting MS-Word Developer Toolbar to show",LogTypeInfo
      RegPath = "HKEY_USERS\Test\Software\Microsoft\Office\14.0\Word\Options\"
      oshell.RegWrite Regpath & "DeveloperTools", "1", "REG_SZ"
      If Err<>0 Then 
        oLogging.CreateEntry sSName & ": Failed to update S-word developer tools settings",LogTypeError
        Exit Function
      End If
    3. change the SDL-Trados licensing server IP:
      oLogging.CreateEntry sSName & ": Setting Default User Trados license server",LogTypeInfo
      RegPath = "HKEY_USERS\Test\Software\Trados\Shared\Licence"
      oshell.RegWrite Regpath & "Licence_file", "27000@", "REG_SZ"
      If Err<>0 Then 
        oLogging.CreateEntry sSName & ": Failed to update Default User Trados license server setting",LogTypeError
        Exit Function
      End If
      oLogging.CreateEntry sSName & ": Setting Default User Screensaver timeout settings",LogTypeInfo
      RegPath = "HKEY_LOCAL_MACHINE\SOFTWARE\FLEXlm License Manager"
      oshell.RegWrite Regpath & "Trados_License_File", "27000@;27000@xlcs4sbynj1www", "REG_SZ"
      If Err<>0 Then 
        oLogging.CreateEntry sSName & ": Failed to update Screensaver to timeout settings",LogTypeError
        Exit Function
      End If
  5. On Ghost:
    1. We create a Ghost file task that points to the wsf file with the current changes we want to implement:
    2. imageimage 
      1. image To apply other changes, just change the filename of your script , e.g.: clip_image001
    3. to apply to other computers, just change the target in the ghost task.
  6. Output:
    1. image
    2. These scripts use the ZTIUtility.vbs from the MDT.
      1. You may have to update the location: <script language="VBScript" src="ZTIUtility.vbs"/>.
      2. For a while, the logging success made me believe I I had accessed the ntuser.dat and had run into registry permission settings loading it. In fact, I just did not resolve to the XP path of the ntuser.dat. Take advantage of the the logging facilities that come with MDT: Here are your logs on the client: image.
      3. Read the logs with TRACE32, part of the SMS 2003 Toolkit 2.
  7. Result: Provided the client has been cleanly frozen, and the domain user has no profile created before on this machine, and his profile is based on the altered default user profile, his HKCU will inherit the changes: image image

How to query lab computers for new IPs after network reconfiguration using Symantec Ghost

Protected: How to boot to thawed or frozen, using Symantec-Ghost file action or Deepfreeze proper

2012/03/01 Enter your password to view comments.

This content is password protected. To view it please enter your password below:

Failure due to timeouts when capturing image from Symantec-Ghost

  1. do not thin I Have not seen that before: image capture starts successfully, but  client times out in the middle; happens repeatedly both during the day and at night?
  2. symantec-client-timed-out
  3. What else to try? symantec-client-timed-out1
  4. Solution/workaround: inconclusive. First try w/o Deepfreeze installed and with high compression worked. But third try without any changes had also finally succeeded (although deploying that image was not tested).

Symantec Ghost Software inventory of the LRC PCs

  1. This list documents the configuration of the LRCRoomCoed434 and LRCRoomCoed433PCs (that are imaged using the Symantec Ghost client).
    1. View here.
    2. LRC staff click here for edit in browser access to the non-embedded list.
    3. Click here for background information about this inventorying method.

Streaming Problems with Realmedia via RTSP from ereserves with VLC Player (and Internet Explorer. And NetOp School)

  1. VLC-player
    1. version 1.1.9,  but also currently newest 1.1.11 as well on Windows CXP SP 3
    2. opens from IE8 and Firefox 3.6
    3. but is not able to play files (tested even multi) through. Rather, it nicely falls on its face, with the audio stream simply appearing to stop, mid-sentence, after 2:38 (pretty consistently – a buffering bug? A great way to slip through pre-testing).
    4. In the LRC, I could hardly bring the taskswitcher up, let alone (15 minutes of waiting) the task manager, to even find that vlc.exe is the culprit, with a CPU utilization of 99% solid (Ouch!). ereserves (4)
    5. Not quite so bad in the office computer where it hovered slightly above 25%, maybe busying  only one CPU core. ereserves-crashes-vlcplayer-at238-diana
  2. My Google searches do not find anything quite similar.
  3. RealPlayer 14 to the rescue?
    1. In IE8, RealPlayer does not open when clicking on the web page link with the RM file which causes a dialogue to open if VLC-player is the default player, rather a strange unplayable content error..
    2. realplayer-cannot-open-ram-from-ereserves-in-ie8
    3. In Firefox, RealPlayer open and plays (and pre-buffers) the stream completely.realplayer-cannot-open-ram-from-ereserves-but-from-firefox
    4. Note that ereserves “download as zip” cannot serve as a workaround: gives you only the links like, which require you to re-authenticate, even if in the same browser session, and do not redirect to the resource, neither audio nor web page form which you could launch the audio (in short, I do not get what this download as zip is good for)
    5. Next Problem: This may work on my office computer. In the lab we have NetOp School installed. That adds another layer of NetOp School problems which look like they can be resolved next time the lab is reimaged. For now, use instead audio from Moodle metacourses where possible. next time I get around to design and run a Symantec-Ghost Software and File Action on the computers (all LRC lab PCs) and test the result (on PC10) which was now.