S
Samsung
Hello Everyone,
Installed a program on our network a few months ago and have worked out a
lot of the kinks and issues with it. Thought I would share those things
with you for anyone that may have such issues with this program in the
future. First a little introduction to the program so everyone knows what
it is, then the issues I had and how I solved them in Windows XP.
Deep Freeze, as I am sure everyone knows, is a fascinating little program
which when installed on Windows, it will save the configuration of the
entire drive and restore it back to the way it was upon rebooting the
computer. I use it to save my 'C:' drive. Anything that is installed on my
computer and any changes that are made to it go back to its original state
upon reboot. This includes little nasty programs like viruses and spyware
and the such like. It basically provides peace of mind for those with
computers that either go through a lot of installations and changes, or
those whose computers are used by the rest of the family.
The issues I had with Deep Freeze are the following:
a.. Needed to allow people to save things on the C: drive in a certain
folder, without changes disappearing upon reboot.
b.. Wanted people to be able to change and keep profile changes, such as
the background desktop.
c.. Wanted to be able to use Offline Caching, without it reverting back to
its old configuration upon reboot.
d.. Wanted to be able to keep the Event Logs, without them reverting back
to their old configuration upon reboot.
Solution to Saving Information
The solution to most of these issues, including this one, was basically to
create another partition, then redirect.
I created a 'D:' drive and called it 'Data' where changes can be stored and
kept. Although the professional version of Deep Freeze has the ability to
create a 'virtual drive' where these changes can be kept, I would recommend
it. A 'virtual drive' is not seen unless the operating system is up and
running and would be very difficult to retrieve information on it upon total
failure of the computer.
One of my issues was the fact that one of our very old programs saved some
output to a folder on the root drive called "Billing". To get around the
issue of losing the "Billing" information upon reboot, I created the folder
on the D:/ drive and used a program called JUNCTION to created a 'symbolic
link' on the C:/ drive.
The results was a 'virtual' folder on the C:/ drive called Billing which
actually saves everything on the 'real' folder on the D:/ drive.
Solution to Keeping Profile Changes
The next issue was allowing people to change and keep their profiles
changes. There are a few solutions to this and I will go over it with you
as well as the quirky things that happened in my testing.
For profile changes, Faronics has a program on their website called
MappingTool which is supposed to somehow re-direct such folders and allow
you to keep such changes. More about this can be found on the Faronics
website in a whitepaper that talks about this issue. This is not what I
did, thus I cannot write more about it. I will say however that it is
possible to come across a certain issue of profile duplication that is
listed below in another solution I tried.
Another way I tried was to create a folder on the D:\ drive and call it
Documents and Settings (exactly the way it is on the C: drive). I then
created the profile in a 'thawed' mode and restarted the computer to get out
of the profile all together. I then logged on as the administrator and
copied the profile to the D:\ drive, then went into the registry to change
the location of where Windows should find the directory. The registry key
locations are found at:
\\My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\{Bunch of Numbers}
(this registry location has only been confirmed for Windows XP)
Find the setting that points to the profile saying something like,
"%systemroot%\Documents and Settings\{username}" and change it to
"D:\Documents and Settings\{username}"
Issues in resolving the Profile Savings Solution
The issue with doing this is that you must do it individually with each user
as the profile is created. You see, the profile is a combination of the
files in the Documents and Settings, and the registry that points to those
files.
Although the files are saved on the D:\ drive, and thus do not revert back
to their original configuration upon reboot, the registry however is saved
on the C:\ drive, and it DOES revert back to its original configuration.
Each time a new profile is created in Windows, it puts an entry in the
registry telling Windows where to find the profile for the user, then it
puts the 'Default Profile' files in that location.
For a good idea about what this scenario could cause, you can try changing
the location in the registry that points to where these files could normally
go and cause it to save the new default location to the D:\ drive.
What would happen is, if a new profile is created in a frozen mode, it will
put the files on the D:\ drive and put a setting in the registry as to where
to find the files. Upon reboot however, the registry will revert back to
what it was without the new profile entry, and the files on the D:\ drive
will remain. Thus, when the new user logs in again, not finding an entry in
the registry to the new profile, it will attempt to create the files again
on the D:\ drive and put an entry in the registry again to the new files.
However, the files will already be there. Windows will think this is
another profile from some other time and create new files and a new
location. This will literally repeat itself several times until you have a
full drive filled with new profiles.
Another solution to the Profile Savings
Another solution was for me to use Roaming Profiles. For those familiar
with Roaming profiles, you must have to log on to a Domain Controller to use
Roaming Profiles, and this solution would not be for the average home user.
For those interested in this solution however, this works quite well. The
only problem is that the computer has a slow log on each time the profile is
downloaded from the server and placed on the computer anew.
To fix the issue of a slow logon each time the profile is saved anew to the
C:\ drive was to use the Domain Policies and 'not' save the 'Desktop' nor
the 'My Documents' folders in the profile, which is where most users would
have the most information. Then I redirected those folders to a server
where I could successfully back them up on a regular basis.
Another issue I had with Roaming Profiles however was in saving a picture on
the Desktop. Seemed like sometimes it worked and sometimes it didn't. I
found out that the issue wasn't with the Roaming Profiles but rather with
Active Desktop. It appears that when a picture in a jpg format is saved on
the Desktop, it utilizes Active Desktop and automatically transforms the
picture so it can be displayed, and putting some registry entries in the
computer (remember that the registry is in a frozen state).
I never did find a fix for it, but I was able to get around it. Simply
convert the jpg to a bmp file, and turn off the Active Desktop through the
Domain Policies. Bmp files seem to stick while only jpg files have an
issue.
Solution to Offline Caching of Networked Drives
I came across this issue mostly with laptops that were sometimes removed
from the network for use in the field. I needed a way for people to save
things to their laptop, usually 'My Documents' without the Offline Caching
reverting back to it's old state (since it is stored on the C: drive)
For this solution, I went into Safe Mode and used a program called
CacheMov.exe from the Microsoft Server Resource Kit (do a google search on
this one). Works great.
For those without access to CacheMov, another program called Junction also
works good. Just move the hidden CSC folder to the D:/ drive, then use
junction to create a 'symbolic link' (UNIX Lingo) to that folder. The
command would be something like:
JUNCTION C:\CSC D:\CSC
I have not had any issues with this, other than the fact that it needs to be
done in Safe Mode.
Solutions to Saving the Event Logs
Another simple solution, just save the event logs on the D:/ drive. Create
your folder "I call mine Event Logs" on the D:/ drive and redirect the
registry setting to point there. The registry location can be found at:
"\\My
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog"
I have not had any issues with doing this either.
Installed a program on our network a few months ago and have worked out a
lot of the kinks and issues with it. Thought I would share those things
with you for anyone that may have such issues with this program in the
future. First a little introduction to the program so everyone knows what
it is, then the issues I had and how I solved them in Windows XP.
Deep Freeze, as I am sure everyone knows, is a fascinating little program
which when installed on Windows, it will save the configuration of the
entire drive and restore it back to the way it was upon rebooting the
computer. I use it to save my 'C:' drive. Anything that is installed on my
computer and any changes that are made to it go back to its original state
upon reboot. This includes little nasty programs like viruses and spyware
and the such like. It basically provides peace of mind for those with
computers that either go through a lot of installations and changes, or
those whose computers are used by the rest of the family.
The issues I had with Deep Freeze are the following:
a.. Needed to allow people to save things on the C: drive in a certain
folder, without changes disappearing upon reboot.
b.. Wanted people to be able to change and keep profile changes, such as
the background desktop.
c.. Wanted to be able to use Offline Caching, without it reverting back to
its old configuration upon reboot.
d.. Wanted to be able to keep the Event Logs, without them reverting back
to their old configuration upon reboot.
Solution to Saving Information
The solution to most of these issues, including this one, was basically to
create another partition, then redirect.
I created a 'D:' drive and called it 'Data' where changes can be stored and
kept. Although the professional version of Deep Freeze has the ability to
create a 'virtual drive' where these changes can be kept, I would recommend
it. A 'virtual drive' is not seen unless the operating system is up and
running and would be very difficult to retrieve information on it upon total
failure of the computer.
One of my issues was the fact that one of our very old programs saved some
output to a folder on the root drive called "Billing". To get around the
issue of losing the "Billing" information upon reboot, I created the folder
on the D:/ drive and used a program called JUNCTION to created a 'symbolic
link' on the C:/ drive.
The results was a 'virtual' folder on the C:/ drive called Billing which
actually saves everything on the 'real' folder on the D:/ drive.
Solution to Keeping Profile Changes
The next issue was allowing people to change and keep their profiles
changes. There are a few solutions to this and I will go over it with you
as well as the quirky things that happened in my testing.
For profile changes, Faronics has a program on their website called
MappingTool which is supposed to somehow re-direct such folders and allow
you to keep such changes. More about this can be found on the Faronics
website in a whitepaper that talks about this issue. This is not what I
did, thus I cannot write more about it. I will say however that it is
possible to come across a certain issue of profile duplication that is
listed below in another solution I tried.
Another way I tried was to create a folder on the D:\ drive and call it
Documents and Settings (exactly the way it is on the C: drive). I then
created the profile in a 'thawed' mode and restarted the computer to get out
of the profile all together. I then logged on as the administrator and
copied the profile to the D:\ drive, then went into the registry to change
the location of where Windows should find the directory. The registry key
locations are found at:
\\My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList\{Bunch of Numbers}
(this registry location has only been confirmed for Windows XP)
Find the setting that points to the profile saying something like,
"%systemroot%\Documents and Settings\{username}" and change it to
"D:\Documents and Settings\{username}"
Issues in resolving the Profile Savings Solution
The issue with doing this is that you must do it individually with each user
as the profile is created. You see, the profile is a combination of the
files in the Documents and Settings, and the registry that points to those
files.
Although the files are saved on the D:\ drive, and thus do not revert back
to their original configuration upon reboot, the registry however is saved
on the C:\ drive, and it DOES revert back to its original configuration.
Each time a new profile is created in Windows, it puts an entry in the
registry telling Windows where to find the profile for the user, then it
puts the 'Default Profile' files in that location.
For a good idea about what this scenario could cause, you can try changing
the location in the registry that points to where these files could normally
go and cause it to save the new default location to the D:\ drive.
What would happen is, if a new profile is created in a frozen mode, it will
put the files on the D:\ drive and put a setting in the registry as to where
to find the files. Upon reboot however, the registry will revert back to
what it was without the new profile entry, and the files on the D:\ drive
will remain. Thus, when the new user logs in again, not finding an entry in
the registry to the new profile, it will attempt to create the files again
on the D:\ drive and put an entry in the registry again to the new files.
However, the files will already be there. Windows will think this is
another profile from some other time and create new files and a new
location. This will literally repeat itself several times until you have a
full drive filled with new profiles.
Another solution to the Profile Savings
Another solution was for me to use Roaming Profiles. For those familiar
with Roaming profiles, you must have to log on to a Domain Controller to use
Roaming Profiles, and this solution would not be for the average home user.
For those interested in this solution however, this works quite well. The
only problem is that the computer has a slow log on each time the profile is
downloaded from the server and placed on the computer anew.
To fix the issue of a slow logon each time the profile is saved anew to the
C:\ drive was to use the Domain Policies and 'not' save the 'Desktop' nor
the 'My Documents' folders in the profile, which is where most users would
have the most information. Then I redirected those folders to a server
where I could successfully back them up on a regular basis.
Another issue I had with Roaming Profiles however was in saving a picture on
the Desktop. Seemed like sometimes it worked and sometimes it didn't. I
found out that the issue wasn't with the Roaming Profiles but rather with
Active Desktop. It appears that when a picture in a jpg format is saved on
the Desktop, it utilizes Active Desktop and automatically transforms the
picture so it can be displayed, and putting some registry entries in the
computer (remember that the registry is in a frozen state).
I never did find a fix for it, but I was able to get around it. Simply
convert the jpg to a bmp file, and turn off the Active Desktop through the
Domain Policies. Bmp files seem to stick while only jpg files have an
issue.
Solution to Offline Caching of Networked Drives
I came across this issue mostly with laptops that were sometimes removed
from the network for use in the field. I needed a way for people to save
things to their laptop, usually 'My Documents' without the Offline Caching
reverting back to it's old state (since it is stored on the C: drive)
For this solution, I went into Safe Mode and used a program called
CacheMov.exe from the Microsoft Server Resource Kit (do a google search on
this one). Works great.
For those without access to CacheMov, another program called Junction also
works good. Just move the hidden CSC folder to the D:/ drive, then use
junction to create a 'symbolic link' (UNIX Lingo) to that folder. The
command would be something like:
JUNCTION C:\CSC D:\CSC
I have not had any issues with this, other than the fact that it needs to be
done in Safe Mode.
Solutions to Saving the Event Logs
Another simple solution, just save the event logs on the D:/ drive. Create
your folder "I call mine Event Logs" on the D:/ drive and redirect the
registry setting to point there. The registry location can be found at:
"\\My
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog"
I have not had any issues with doing this either.