I'm incredibly impressed by this 6th generation VM tech they have out now. This is a lot better than even the offerings from a couple years ago.<br><br><div class="gmail_quote">On Dec 7, 2007 2:00 PM, Cyber Source <
<a href="mailto:peter@thecybersource.com">peter@thecybersource.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Oh yea, we use VMware converter here all the time. I use ntfsresize to
<br>reduce the use of windows on the hard drive, make room for linux, make a<br>vm out of the boot side and then run it under the Linux side, voila!<br>They now can experience Linux and have their windows stuff a click away.
<br>And, business is boomin.<br><div class="Ih2E3d"><br>Brad Bartram wrote:<br>> Believe it or not, I'm finding that creating the VM is a little easier.<br>><br>> VMWare makes a nice little utility for making a virtual machine out of
<br>> a harddrive image. It's called VMware-converter - and it's free.<br>><br>> If the machine is running, just fire up this app and set it up to do<br>> its thing using the wizard. The vm gets created.
<br>><br>> We did it once with the full laptop drive, which turned into a<br>> performance nightmare because of all the crap he runs - it is a<br>> windows laptop afterall, but it booted right away. We decided it
<br>> would be best to remove some of the startup stuff and then do a<br>> reimage. We popped the old harddrive into a new laptop, fired up the<br>> os, ran the vmware software, and voila - problem solved.<br>>
<br>> BTW - I am very impressed with vmware fusion. If you run a mac, I<br>> would recommend you think about it for virtualization needs.<br>><br>> Thanks for all the help guys. As always, whenever I beat my head
<br>> against a wall, I know someone on this list can usually recommend<br>> something.<br>><br>> Brad<br>><br>> On Dec 7, 2007 1:16 PM, Cyber Source <<a href="mailto:peter@thecybersource.com">peter@thecybersource.com
</a><br></div><div class="Ih2E3d">> <mailto:<a href="mailto:peter@thecybersource.com">peter@thecybersource.com</a>>> wrote:<br>><br>> If you can find that *.pst file, you'll save yourself tons of time
<br>> and agro.<br>><br>> Brad Bartram wrote:<br>> > From my research, I've found that Outlook2007 has things thrown all<br>> > over the place in various files and registry settings and keys.
<br>> Right<br>> > now I have two things going on, I've figured out the registry keys<br>> > being used, so I'm hacking them into the current system. I'm also<br>> > imaging the entire drive for a vmware virtual machine.
<br>> ><br>> > I'll see how these things work.<br>> ><br>> > I'll post a result as something happens so everyone can stop<br>> anxiously<br>> > holding their breath in anticipation. ;-)
<br>> ><br>> > Brad<br>> ><br>> > On Dec 7, 2007 12:20 PM, Cyber Source <<a href="mailto:peter@thecybersource.com">peter@thecybersource.com</a><br>> <mailto:<a href="mailto:peter@thecybersource.com">
peter@thecybersource.com</a>><br></div>> > <mailto: <a href="mailto:peter@thecybersource.com">peter@thecybersource.com</a><br><div><div></div><div class="Wj3C7c">> <mailto:<a href="mailto:peter@thecybersource.com">
peter@thecybersource.com</a>>>> wrote:<br>> ><br>> > Not sure about the newer versions but Outlook from Office<br>> 2000 would<br>> > make a backup *.pst file by default. I've used this before.
<br>> Search<br>> > through the old data for *.pst, I believe it will be called<br>> > backup.pst,<br>> > import that file and you should have all as it was.<br>> >
<br>> > Brad Bartram wrote:<br>> > > Hey guys,<br>> > ><br>> > > First, sorry about the off topic post, but I know there's<br>> probably<br>> > > some knowledge on the subject here, so I figured I'd give
<br>> it a try.<br>> > ><br>> > > Here's my issue:<br>> > ><br>> > > A person I work with is using Outlook 2007 for his mail and<br>> > personal
<br>> > > scheduling and address book and keeping his food cold,<br>> etc. He<br>> > > recently had his laptop crap out on him. Long story short, we<br>> > have a<br>
> > > new machine for him, but he wants to migrate his old settings<br>> > and such<br>> > > from his old harddrive image over to his new machine. He has<br>> > all his
<br>> > > old email in the form of a pst, as well as complete access to<br>> > the old<br>> > > drive including the registry.<br>> > ><br>> > > From my preliminary research, I found that outlook stores
<br>> account<br>> > > information in the registry (go figure). His big concern<br>> is the<br>> > email<br>> > > filters he has set up to move his mail all around. He has
<br>> quite a<br>> > > complex ruleset and isn't really looking forward to recreating<br>> > it from<br>> > > scratch - and neither do I, because I sit right next to
<br>> him and it<br>> > > just won't make my day pleasant.<br>> > ><br>> > > So does anyone here know where outlook 2007 stores the<br>> filter data?<br>
> > ><br>> > > The only thing we don't have access to at this point is a<br>> running<br>> > > machine with his native OS and Data on it, we're working<br>
> from an<br>> > > image, so I can't just fire up his old OS and run an export or<br>> > > migration application or utility on it.<br>> > ><br>> > > Any help would be appreciated.
<br>> > ><br>> > > Thanks<br>> > ><br>> > > Brad<br>> > ><br>> ><br>> ------------------------------------------------------------------------
<br>><br>> > ><br>> > > _______________________________________________<br>> > > nflug mailing list<br></div></div>> > > <a href="mailto:nflug@nflug.org">
nflug@nflug.org</a> <mailto:<a href="mailto:nflug@nflug.org">nflug@nflug.org</a>> <mailto:<br><div class="Ih2E3d">> <a href="mailto:nflug@nflug.org">nflug@nflug.org</a> <mailto:<a href="mailto:nflug@nflug.org">
nflug@nflug.org</a>>><br>> > > <a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">http://www.nflug.org/mailman/listinfo/nflug</a><br>> > ><br>> > _______________________________________________
<br>> > nflug mailing list<br>> > <a href="mailto:nflug@nflug.org">nflug@nflug.org</a> <mailto:<a href="mailto:nflug@nflug.org">nflug@nflug.org</a>><br></div>> <mailto:<a href="mailto:nflug@nflug.org">
nflug@nflug.org</a> <mailto:<a href="mailto:nflug@nflug.org">nflug@nflug.org</a>>><br><div><div></div><div class="Wj3C7c">> > <a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">http://www.nflug.org/mailman/listinfo/nflug
</a><br>> ><br>> ><br>> ><br>> ------------------------------------------------------------------------<br>> ><br>> > _______________________________________________
<br>> > nflug mailing list<br>> > <a href="mailto:nflug@nflug.org">nflug@nflug.org</a> <mailto:<a href="mailto:nflug@nflug.org">nflug@nflug.org</a>><br>> > <a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">
http://www.nflug.org/mailman/listinfo/nflug</a><br>> ><br>> _______________________________________________<br>> nflug mailing list<br>> <a href="mailto:nflug@nflug.org">nflug@nflug.org</a> <mailto:
<a href="mailto:nflug@nflug.org">nflug@nflug.org</a>><br>> <a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">http://www.nflug.org/mailman/listinfo/nflug</a><br>><br>><br>> ------------------------------------------------------------------------
<br>><br>> _______________________________________________<br>> nflug mailing list<br>> <a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br>> <a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">
http://www.nflug.org/mailman/listinfo/nflug</a><br>><br>_______________________________________________<br>nflug mailing list<br><a href="mailto:nflug@nflug.org">nflug@nflug.org</a><br><a href="http://www.nflug.org/mailman/listinfo/nflug" target="_blank">
http://www.nflug.org/mailman/listinfo/nflug</a><br></div></div></blockquote></div><br>