Best practice - moving home directories

Hello all,
I was looking for insight on best practices for moving home directories.
I was thinking that using the migration tool would be best to move the directories and then using dsrazor to remap all of the home directories for our users.
We are running Netware 6.5 SP8. I have added a 2TB RAID 10 set to one of our servers which is where I am planning on moving all of the user directories.
Thoughts/suggestions are welcome.
Steve D.

Originally Posted by sjdimare
Moving data from one volume to another on the same server should not require migration, correct? I just want to make sure all of the trustee assignments stay in place.
I also will need to redo volume space restriction on new user templates and the migrated volumes.
First test went quite smoothly.
Steve D.
When you move data (using Windows explorer ect) across volumes the trustee rights drop off. If moving from NW to NW use Server Consilidation and Migration Tool. If moving from NW to OES Linux use miggui. The SCMT has a few other features like project planning and verification.

Similar Messages

FCPX 10.1: Best practice moving libraries (files)?

In the past, FCPX encouraged us to moves files WITHIN the application, through the UI.
Does 10.1. now encourage us to move/delete files (libraries) "under the hood?"--in the finder? Given a choice, what is the best practice?

Hi dostoelk,
Welcome to the Support Communities!
Clips, projects, and events should still be managed within Final Cut Pro X. For more information, read our Managing Media with Final Cut Pro X Libraries white paper (PDF) at: www.apple.com/final-cut-pro/docs/Media_Management.pdf
I hope this information helps ....
Happy Holidays!
- Judy

Moving Home Directories

I have 2 Xserves running OSX Server 10.4.10 ,the OD master is in New York and the replica in Paris.
I have 3 user groups: AllEmployee, NYEmployee and ParisEmployee.
I have Mobility preferences managed for every user (AllEmployee), Background sync enabled and always managed, synching client home directories, skipping ~/Library .
New York users homes are replicated to the NewYorkServer/Users
Paris users homes are replicated to the ParisServer/Users
Now the questions:
1) I have to move one user from New York to Paris. What's the correct procedure to migrate her home folder to the paris server?
2) Anyone why the exclusion of ~/Library works as expected using a Tiger client, but doesn't using Leopard? (both users are not admin of the machines).
Thank you!
Federico

There's about 8 pages in the Migration guide devoted to migrating from Server 10.3:
http://www.apple.com/server/documentation/
download of the 1 MB , 97 page document starts when you click on second one down, called:
"Upgrading and Migrating [to Server 10.4]"
... you may also have it on your Server 10.4 CD/DVD set.

Moving home directories best practice

I have storage manager 2.5 installed and working well and my users managed. I have about 200 users in different OUs that I want to move storage from one NW65 to another NW65. How do I go about doing this in a smooth fashion without downtime for the users. I would go slowly and mig them over about 10 at a time. I did a quick search and didn't find much. Is there somewhere that explains it? Thanks

mfairpo,
I would follow the steps that you guys have already talked about.
Run a Consistency Check to make sure all the users are managed, and that
not none of the home directory paths are pointed to the root of the
volume, etc.
Update the Policy to reflect the change in target path.
Run the Enforce Policy Path management action, but use the MASK field to
move a few at a time. "a*" will move the users whose CN starts with a.
If you want to move several letters at a time you can use "a*|b*" to
move the users who start with a OR b.
Use the move schedule if you don't want NSM to do the work during the
business day.
NSM will make sure that the user is logged out before attempting to move
their storage. The event will remaining pending until they logout.
thanks,
NSM Development
On 9/8/2010 10:06 AM, mfairpo wrote:
>
> Yes, a new Target Path (removing the old path) ought cause pending move
> Events upon a back-fill operation (Enforce Policy Paths). However, we
> also set Rename Inhibit + Delete Inhibit attributes in all policy.
> Whilst I can unset these, I wish some clear guidance.
>
>

Best Practice Moving to iPrint Appliance

I'm working with a site that has some old NDPS printing on NetWare 6.5 and some OES based iPrinting. We are moving to the iPrint appliance. While you can migrate/import printers from the old system into the appliance, I haven't figured out the best way to deal with the clients. What have others done to switch the clients over to the appliance based printers? Are there any tricks here? Looking for what others have done. Thanks.
Matt

matt,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Forums Team
http://forums.novell.com

Best practice for home setup/Roaming with built-in Dell wireless card?

I have a client with a huge house; I have done a site survey and it will require 3 APs to blanket the entire thing. I am wonderig what the best way to set this up for him would be? He would like to be able to walk around with the house and not lose connectivity. He is attempting to use his built-in Dell wireless card/client. As far as I know, these do not support Cisco roaming. What I have done is setup 3 diffrent SSIDs for each part of the house. Depending on his location he manually connects to the correct AP. Is this the best setup?
I had attempted to set all APs with the same SSIDs but found that the client would not roam and also found it difficult to connect to any of the APs at all. I believe the card was getting confused since there was overlap of the same SSID.

If he has a huge house, I don't think his laptop would be that old and also, the Dell's use the Intel wifi cards. Having all 3 ap's setup for the same SSID is what you should do and don't know why you are having so many issues. I would assume the ap's are on channel 1, 6, and 11 and how is the power setting? Do all these ap's run back to the same switch?

Firewall what is best practice for home use?

Hi (from France) and thanks in advance.
I want to activate firewall but don't know which setting to choose for the right mix of security/ease of use. My Imac connected by ethernet to Dartybox (router) and sharing internet access with my wife's Macbook pro via wifi .

simonfromfra wrote:
The 'dartybox' router has a very poor security rating - so my reading tells me, and is the easiest of all French internet "out of the box all in one" connections to hjack (crack codes well documented)... hence my desire for second layer protection.
Take a look at: IceFloor
IceFloor is not a firewall. Your Mac already features three built-in firewalls:
• ALF
• PF
• IPFW
ALF is an application firewall, while both PF and IPFW are network firewalls.
ALF can be configured using System Preferences “Security” pane.
PF and IPFW do not have a default graphic interface shipped with OS X, so they can be configured only using the shell terminal. Using the terminal is the favourite choice by most system administrators.
Since Mac OS X 10.7 IPFW has been deprecated. PF is the new default OS X network firewall. To configure PF without using the shell terminal we must use a graphic interface (frontend) from third party software makers.
IceFloor is a graphic frontend for PF.
It features a lot of advanced tools and options that will let you set up a very complex PF ruleset.
IceFloor needs OS X 10.7 or newer.
Bandwidth management with PF/Dummynet is supported on OS X 10.8 and newer.
PF ruleset created with IceFloor 2.0 has been tested on:
OS X 10.7 OS X 10.8 OS X 10.9 iOS 5
iOS 6 FreeBSD 9 OpenBSD 4.3
We developed also a limited version of IceFloor named PFLists.
PFLists is a free and open source basic PF frontend with the same requirements as IceFloor 2.

FCP & moving Home Folders

Guys, I'm on Lion and am contemplating moving my Home Folder from my Boot Drive to my 2nd Internal HD.
Will this have any adverse and negative effects on any of the Final Cut Studio applications?
I store all my video files and projects on the 2nd internal HD. Nothing is stored on the Boot drive exept for Applications and my iTunes and iPhoto files.
The reason for wanting to do this is my wife and I both have separate accounts. Right now, I do not store any documents (Pictures, Movies etc) on my Boot Drive. All of this is stored on my second internal drive.
Unfortunately, this does not allow my wife and I to separate our documents. She has access to mine and I to hers.
But I want to be able to only access the docs for the person whose account has been logged in to.

edited --
If you have independant user accounts (even if they are admin) you should not be able to see the documents, pictures, ect. folders of the other person so I don't understand the issue of access.
Here is a way to deal with it that doesn't involve moving home directories.
Set up a new account for administration. You'll need it for installations and/or to make system changes. Make sure it has administrator privliges. Remember the password!.
Then, change your wife's and your accounts to "standard". This will remove ability to override the "no access" as long as you stay within a standard acct. You will have access to shared public and site folders.
To run backups, install software, etc, log into the machine with the admin account. If nothing else, it makes it harder to screw up the machine as you have to go to a bit extra to make changes.
x

Best Practice for Portable Home Directories

What are the 'best practice' directories to sync for Portable Homes - at login and in the background. I want to make my user experience a little better than it is now.
Login and logout take about 2 minutes - even over ethernet 100Mb, and longer using Airport, and 'background' home directory syncing seems to always suck all of my network bandwidth - making apps like Safari unusable - even though I have barely changed anything in the folders I am syncing.
My personal home directory is 1.5Gb, and I keep my Music, Pictures and Movies on the network - as Apple suggest.

I generally recommend the following for the least impact on user experience:
1. Put your server and clients that will use mobile accounts and portable homes on a Gigabit Ethernet switch. It's a small price to pay for much more customer satisfaction.
2. Put more RAM in the server, especially if you're dealing with a few users with large homes or several users with moderately-sized (less than 1.0GB) ones. This will also let you employ server-side tracking (for 10.5 server).
3. Only sync and login/logout. Use Workgroup Manager to define all portable preferences. Choose to manage login/logout sync, and specify the items to sync; for the whole home, use "~". Omit things like ~/.Trash. Choose to manage the background sync, but remove all items from the "sync these items" list. Choose to manage the background sync interval by setting it to manual. This way, the user doesn't accidentally configure a background sync: we've told it to sync nothing only we say it can.
--Gerrit

Best Practice(s) for Laptop in Field, Server at Home? (Lightroom 3.3)

Hi all!
I just downloaded the 30-day evaluation of Lightroom, now trying to get up to speed. My first task is to get a handle on where the files (photos, catalogs, etc.) should go, and how to manage archiving and backups.
I found a three-year-old thread titled "Best Practice for Laptop in Field, Server at Home" and that describes my situation, but since that thread is three years old, I thought I should ask again for Lightroom 3.3.
I tend to travel with my laptop, and I'd like to be able to import and adjust photos on the road. But when I get back home, I'd like to be able to move selected photos (or potentially all of them, including whatever adjustments I've made) over to the server on my home network.
I gather I can't keep a catalog on the server, so I gather I'll need two Lightroom catalogs on the laptop: one for pictures that I import to the laptop, and another for pictures on the home server -- is that right so far?
If so, what's the best procedure for moving some/all photos from the "on the laptop catalog" to the "on the server catalog" -- obviously, such that I maintain adjustments?
Thanks kindly! -Scott

Hi TurnstyleNYC,
Yes, I think we have the same set-up.
I only need 1 LR-catalog, and that is on the laptop.
It points to the images wherever they are stored: initially on the laptop, later on I move some of them (once I am am fairly done with developing) within LR per drag&drop onto the network storage. Then the catalog on the laptop always knows they are there.
I can still continue to work on the images on the network storage (slightly slower than on laptop's hard drive) if I still wish to.
While travelling, I can also work on metadata / keywording, although without access to my home network the images themselves are offline for develop work.
2 separate catalogs would be very inconvenient, as I would always have to remember if I have some images already moved. No collections would be possible of images including some on the laptop, some on the network.
Remember: a LR catalog is just a database with entries about images and the pointer to their storage location.
You can open only 1 DB of this sort at a time.
There is no technical reason for limiting a LR-catalog - I have read of people with several hundert thousand images within one.
The only really ever growing part on my laptop with this setup is the previews folder "<catalog name> Previews.lrdata". I render standard previews so that I can do most of the work for offline-images while travelling.
The catalog itsself "<catalog name>.lrcat" grows much slower. It is now 630 MB for 60'000+ images, whereas previews folder is 64 GB.
So yes, I dedicate quite a junk of my laptop hard disk to that. I could define "standard"-previews somewhat smaller, fitting to the laptop's screen resolution, but then when working at home with a bigger external monitor LR would load all the time for the delta size, which is why I have defined standard-preview-size for my external monitor. It may turn out to be the weakness of my setup long-term.
That is all what is needed in terms of Lightroom setup.
What you need additionally to cover potential failure of drives is no matter of LR, but *usual common backup sense* along the question "what can be recreated after failure, if so by what effort?" Therefore I do not backup the previews, but very thoroughly the images themselves as well as the catalog/catalog backups, and for convenience my LR presets.
Message was edited by: Cornelia-I: sorry, initially I had written "1:1-previews", but "standard previews" is correct.

Best practice for moving from a G5 to a new Mac with SL

I am receiving my new iMac today (27") and am very excited
However I want to move over using the best practices to assure that I remain excited and not frustrated
My initial thoughts are to boot it up and doe the initial set up - to move my iPhoto library over and to use migration assistance to move the rest of my data files
Then to install all of the extra software that I can find the packages for from the original installation disks
And then finally to use migration assistant again to move over any software that I can not find original disks for (I've moved from Mac to Mac to Mac over and over and some of the software goes back to OS 9 (and won't run anymore I guess)
Is this a good way
OR
will I mess up doing it this way
OR
am I spending far too much time worrying about moving old problems over and would be better off to just turn MA loose and let it do its thing form the beginning?
BTW - mail crashes a lot on my existing system - pretty much everything else seems ok - except iPhoto is slow - hoping that the new Intel dual core will help that
LN

Migration Assistant is not a general file moving tool. MA will migrate your Applications and Home folders transferring only your third-party applications. MA will transfer any application support folders required by your applications, your preferences, and network setup. You do not have a choice of what will be migrated other than the above. MA cannot determine whether anything transferred is compatible with Snow Leopard. I recommend you look at the following:
A Basic Guide for Migrating to Intel-Macs
If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.
Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:
Classic Environment, and subsequently any Mac OS 9 or earlier applications
Screensavers written for the PowerPC
System Preference add-ons
All Unsanity Haxies
Browser and other plug-ins
Contextual Menu Items
Applications which specifically require the PowerPC G5
Kernel extensions
Java applications with JNI (PowerPC) libraries
See also What Can Be Translated by Rosetta.
In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.
If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.
If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.
The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.
Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior 4.1, TechTool Pro 4.6.1, SuperDuper 2.5, and Drive Genius 2.0.2 work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.
Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.
Additional links that will be helpful to new Intel-Mac users:
Intel In Macs
Apple Guide to Universal Applications
MacInTouch List of Compatible Universal Binaries
MacInTouch List of Rosetta Compatible Applications
MacUpdate List of Intel-Compatible Software
Transferring data with Setup Assistant - Migration Assistant FAQ
Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode, copying the critical contents to CD and DVD, an external hard drive, or networking
will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.
If both computers support the use of Firewire then you can use the following instructions:
1. Repair the hard drive and permissions using Disk Utility.
2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.
3. Connect a Firewire cable between your old Mac and your new Intel Mac.
4. Startup your old Mac in Target Disk Mode.
5. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.
If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)
1. Set up a local home network: Creating a small Ethernet Network.
2. If you have a MacBook Air or Late 2008 MacBook see the following:
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- Migration Tips and Tricks;
MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
MacBook Air- Migration Tips and Tricks;
MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.
Copy the following items from your old Mac to the new Mac:
In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.
In your /Home/Library/ folder:
/Home/Library/Application Support/AddressBook (copy the whole folder)
/Home/Library/Application Support/iCal (copy the whole folder)
Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)
/Home/Library/Keychains (copy the whole folder)
/Home/Library/Mail (copy the whole folder)
/Home/Library/Preferences/ (copy the whole folder)
/Home /Library/Calendars (copy the whole folder)
/Home /Library/iTunes (copy the whole folder)
/Home /Library/Safari (copy the whole folder)
If you want cookies:
/Home/Library/Cookies/Cookies.plist
/Home/Library/Application Support/WebFoundation/HTTPCookies.plist
For Entourage users:
Entourage is in /Home/Documents/Microsoft User Data
Also in /Home/Library/Preferences/Microsoft
Credit goes to Macjack for this information.
If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.
5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.
Written by Kappy with additional contributions from a brody.
Revised 1/6/2009
In general you are better off reinstalling any third-party software that is PPC-only. Otherwise update your software so it's compatible with Snow Leopard.
Do not transfer any OS 9 software because it's unsupported. You can transfer documents you want to keep.
Buy an external hard drive to use for backup.

Home Movie Cataloging - BEST PRACTICES

I have about 200 hours of old home movies on VHS which I am in the process of adding to my iMac. I am wondering about 'best practices' on how much video can be stored inside of iMovie '08, when how much video becomes too much inside of the program, etc.
In a perfect world, I'd like to simply import all of my home videos into iMovie, leave them in the 'library' section, and make 2-5 minute long clips in the 'projects' section for sharing with family members, but never deleting anything from the 'library'. Is this a good way to store original data? Would it be smarter to export all of the original video content to .DV files or something like that for space saving, etc?
Can I use iMovie to store and catalog all of my old home movies in the same way I use iPhoto to store ALL of my photos, and iTunes to store ALL of my music/hollywood-movies, etc?

We-ell, since no-one else has replied:
1 hour of DV (digital video in the file system which iMovie uses) needs 13GB of hard disc space.
You have 200 hours of video. 200 x 13 = 2,600 gigabytes. Two point six terabytes. If you put all that on one-and-a-bit 2TB hard discs, and a hard disc fails - oops! - where's your backup? ..Ah, on another one-and-a-bit 2TB hard discs ..or, preferably, spread over several hard discs, so that if one fails you haven't lost everything!
iMovie - the program - can handle video stored on external discs. But are you willing to pay the price for those discs? If so; fine! Digitise all your VHS and store it on computer discs (prices come down month by month).
Yes, you can "mix'n'match" clips between different projects, making all sorts of "mash-ups" or new videos from all the assorted video clips. But you'll need more hard disc space for the editing, too. You could use your iMac's internal hard disc for that ..or use one of the external discs for doing the editing on. That's how professionals edit: all the video "assets" on external discs, and edit onto another disc. That's what I do with my big floorstander PowerMac, or whatever those big cheesegraters were called..
So the idea's fine, as long as you have all the external storage you'd need, plus the backup in case one of those discs fails, and all the time and patience to digitise 200 hours of VHS.
Note that importing from VHS will import material as one long, continuous take - there'll be no automatic scene breaks between different shots - so you'll have to spend many hours chopping up the material into different clips after importing it.
Best way to index that? Dunno; there have been several programs which supposedly do the job for you (..I can't remember their names; I've tried a few: find them by Googling..) but they've been more trouble - and taken up more disc space - than I've been prepared to bother with. I'd jot down the different clips as you create them, either by jotting in TextEdit (simplest) or in a database or spreadsheet program such as Excel or Numbers or similar ..or even in a notebook.
Jot down the type of footage (e.g; 16th Birthday party), name of clip (e.g; 016 party), duration (e.g; 06:20 mins and seconds) and anything else you might need to identify each clip.
Best of luck!

Moving Portable Home Directories from one server to another

I am in the process of migrating users from an older xserve running 10.3 with open directory to a new xserve running 10.5. So far, everything is looking good with the migration, the only major issue I'm running into in my testing is with Portable Home Directories. Presently, the portable home directory on the computer still points to the old server for existing user accounts after they are moved to the new open directory server. On the 10.3 server, the home directories are all mounted under /Volumes/Home, where on Leopard it appears it wants to create the shares under /Volumes/ServerName/Folder. Granted, at present the original server's Home Folders are on a fiber attached raid and in testing I don't have this available. Any suggestions on a way to test easily without moving the raid? Also, is there an easy way to do a mass change on user machines where if I move my raid over to the new server, I can make sure that users data is being backed up to the proper location?
Sorry for the lengthy post, just trying to make sure I'm covering all my bases, heh.

Antonio, thanks for the response. I do have one more question regarding this. On the client side, the mirrors.plist file references the old server FQDN and share name. Because this will be being moved over to the new server, is there an easy method to update the clients mirror plist without breaking the PHD mirror? My big concern here is that either the users will not be able to synchronize phd's or we will have to re-establish all the phd's from the client machines to the server. My thought here is simply using a cname to direct any traffic still trying to hit the old server name to the new server name.

Best Practice: files that should never be moved or deleted

Hi there.
I've just gone through my computer for the first time in a couple of years and done a massive cleanup, but without really knowing the consequences I guess you could say and now things are acting a little strange.
+(I feel silly even writing this, knowing that all the IT heads out there are sighing a unanimous 'what an idiot'.)+
Can anyone please provide a sort of 'best practice' guide for the files/file types that should absolutely be on the harddrive, or in the apps folder, utilities folder, etc? and if there are any that should 'never' be deleted?
.. or even some program that sort of saves you from yourself by keeping those files safe from being a.) moved and b.) deleted
Would be a huge help!
Thanks in advance ~
Message was edited by: BluesySue
Message was edited by: BluesySue

Apple has already hidden about half of the folders on a typical OS X install. The ones that make up the Unix core of the OS. So unless you know how to find those, you'll never have to worry about them.
Aside from that, you just want to keep away from the System folder and any of the Library folders. Nothing else should be too crucial to the OS running.
Of course if you wanted to elaborate on "a little strange" we might be able to be a bit more helpful.

Best Practices for viewing home video on my Mac

Come on people - THERE HAS TO BE A BEST PRACTICE out there for storing and viewing family video!!
I'm the typical dad out there taking photos and video of my kids playing soccer, family trips ect ...
When I get home I hook my camera up to my MacMini (which is hooked up to my Plasma TV - and backed up to an external HD) and within mere seconds, my photos are nicely captured in iPhoto. Friends and family come over, I flip on the MacMini, select iPhoto (or Front Row) and we enjoy great slide shows.
I want to be able to have the same easy access to my videos -flip on my MacMini, start Front Row, view my various home movies, pick one and enjoy the show.
What is the best way to do this?
Current Technology
Canon HV20
iMovie 08
iPhoto 08
Front Row

Thanks for the welcome WC! And thanks for the initial help.
I have never exported video before (sad but true), so I have a couple "Workflow" questions for you or anyone else that knows this stuff
1) Should I assume I just hook my firewire up from my Canon to the MacMini and everything just starts to export?
2) Once exported into iMovie, I assume I can edit out some of the garbage (example - my wife sometimes forgets to turn off the camcorder and she'll video her leg or the ground for minutes at a time - I'd like to trash that.
3) Once edited, how do I move it into iTunes?
I will probably need to take an iMovie class ...

Best practice - moving home directories

Similar Messages

Maybe you are looking for