Dealing with Med-V Errors First time fixes

Summary:
Assuming that Med-v has worked at some time since the user was migrated the following seem to
be the commonest problems:
1. Scenario:
Med-V is not launching applications although it previously did. This might be caused
by the user not waiting for the Med-V Workspace to close down properly.
Action(s)
a)
b)

c)

d)
e)

Whilst logged on as the user in Windows 7, Close the Med-V Agent, from the
Agent within the Notification Area in Windows 7, by selecting Exit
From All Programs choose Windows Virtual PC / Windows Virtual PC and when
the Med-v v2 Production Workspace has Powered Down / Hibernated, doubleclick on it.
If the virtual machine starts up with the F8 boot screen, rather than logged on
with the cached user password, select start in Safe Mode, and if the machine
boots up okay then shut it down afterwards.
Start the Med-V Agent again from All Programs and try logging in with the
cached user password
If this works then test using Access 97 from the Office 97 folder to test Med-V,
followed by any of the users applications.

2. Scenario:
Med-V is launching but remediated applications are not working or launching as
they did previously. The users Med-V XP profile may have become corrupt.
Action(s):
a)
b)
c)

d)
e)
f)
g)
h)

If steps 1a e) fail to fix the problem, repeat 1a b).

If Windows Virtual PC (WVPC) logs in as the user automatically, select Settings
from the top of the WVPC window and deleted the Saved Password
Log off as the user from WVPC and logon using Techsupport 1-4 (password
0911uCaLl( (minus quotes), or using another specifically assigned local admin
user id.
Under Documents & settings rename the specific users profile e.g.
old.fred.bloggs.
Log off as local admin and back on in WVPC as the user with the problem, whose
XP profile will be re-created in WVPC.
Once the profile has loaded log off again from WVPC.
Start the Med-V Agent again from All Programs
As their cached password was deleted, the user will again be prompted to enter
their ad03 user id and password, which they should save. N.B. This can need to
1

i)

be repeated a number of times, so be patient, as the Med-v profile is being

initialised for the user and the Med-v icons are being published in Windows 7
alongside the native programs.
When Med-v agent reveals the Ready status in the Notification Area, Access
97 should be tested and then the users other remediated applications

3. Scenario:
Med-V is launching but Windows 7 is displaying an annoying ccm dll missing error
message. The users SCCM Client on Med-V (Windows XP) is corrupt and needs
repairing; occasionally because the machine has switched subnets
Action(s):
a)

b)
c)

d)

e)
f)
g)

Log off as the user from WVPC and logon using Techsupport 1-4 (password
0911uCaLl( (minus quotes), or using another specifically assigned local admin
user id.
Error messages will display re CCM before and once in WVPC, but ignore these
and click ok on each occurrence.
Run regedit and locate
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Unins
tall and find the Configuration Manager Client DisplayName and double-click
on the InstallSource and copy the following text string
C:\WINDOWS\system32\ccmsetup\{4CD82FBB-0AFC-4864-A08915364DF5F14B}\ (you can use the above if convenient and copy via your
terminal server connection )
Open a command prompt, type cd\ and return and then type cd followed by the
copied text string and press return. From the correct directory now type
client.msi (minus quotes) and press return. Configuration Manager Client
will then re-install , taking a few minutes, and will shutdown the window.
When this has completed run the following command shutdown r t 5,
which forces the re-publishing of applications
Start the Med-V Agent again from All Programs in Windows 7
The users password should be cached and it should load to the Ready state, but
without the previous error message, which is annoying for users, especially if
they do not use any remediated applications

4. Scenario:
When testing applications under Windows Virtual PC, these launch fine for a user,
but despite efforts to re-publish icons in Med-V ("shutdown r t 5" from XP, and
checking that All Users have the icons, but these do not work for the user in Med-V,
but work for Techsupport users in Med-V and perhaps other "tst " user accounts).
2

Action(s):
a)

b)

c)

d)

If the actions for Scenarios 2 & 3 still fail to resolve the issue, and if a user logs
on to another Windows 7 machine and does not have functioning Med-V icons
(a useful test); or another user has full Med-V functionality on the users
machine, whilst they do not (also a useful test), try the following
With the user, ensure that the user has a backup of their current desktop icons,
favourites, printer details, and that you know which PSTS they connect to from
X:, and which additional mail boxes they may have. These details will need readding after the roaming profile is deleted. A large amount of this may still be
stored under f:\desktop refresh, but be careful, as fixing one thing can create
more serious issues for the user.
Contact a Wintel resource for the deletion of the users Windows 7 Roaming
Profile. At the same time as the Wintel resource deleting the roaming profile
from the main northern or southern server, you should be doing the following
Once ready delete the users profile in Windows 7
a. Logon as Techsupport 1-4, stop the Med-V Agent and rename the users XP
profile again in WVPC. Log off and restart the Med-v agent
b. Right-click on the Properties of My Computer on the users machine and
choose Advanced Settings, User Profiles Settings
c. Select the users profile and Delete.
d. Get confirmation from Wintel that the Roaming Profile has been deleted
also and the backup in Bridgend.
e. Log off as TechSupport and get the user to log back on, re-creating their
Roaming profile
f. Repeat steps 2h-i) and hopefully a fresh set of Med-V icons will have been
published.
g. Return the users settings for them from the back up in 4b.

5. Scenario:
Med-V used to work but now does not have an IP address other than an Auto ip
config 169.254.*.* address.

Action(s):
a)

If the machine is connected to an IP phone

i. Unplug the machine from the phones switch
ii. Shut down the machine
iii. Power off the phone, by disconnecting the input cable to the phone
iv. Plug this cable back in, wait for the phone to boot and to get a dial
tone.
v. Plug the machine back into the phone switch port
3

vi. Power up the machine and logon as Techsupport 1-4, verifying that
the windows 7 machine gets an ip address and then that WVPC gets
one also
vii. If this does not work the machine will need moving to a non -802.1x
enabled port.
viii. Gpupdate /force will need to be run and 802.1x checks should be
made (other documentation)
ix. Ideally in that location the machines Windows 7 and WVPC should
run a ping t ad03.local afterwards, as their network cable is
switched from 802.1x disabled to enabled.
x. The plug the machine back in on its original subnet
b. If the machine is not plugged into a phone but displays the same symptoms
i. Follow steps a vi-x. above

6. Scenario:
Despite doing all (or some of the above) the above, applications, particularly CFS,
will not launch Java-based applications needed by CFS users. Med-V may need to be
removed and reinstalled, although this task should not be undertaken lightly, needs
Telecoms assistance and may not be performed by the service desk.
Action(s):
a)

b)

If any of the above Actions fail to resolve the issue, whether WVPC fails to boot,
or CFS fails to load Java applications, a more heavy-handed approach is likely to
be needed, currently unsuitable for a first time fix. This should be referred to the
Windows 7 team, as kit will either need placing on an 802.1x disabled port or to
be moved to one.
For CFS the following should be check, when logged on the to WVPC as
Techsupport1-4:
i. Is J-Initiator 1.3.1.28 installed on WVPC when the live system is
being used and Java applications fail to load (if not get the SCCM
team to deploy, before the user re-tries)
ii. Is J-Initiator 1.8.1.16 installed on WVPC when CFS Archive is being
used and Java applications fail to load(if not get the SCCM team to
deploy, before the user re-tries)