Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 544
  • Last Modified:

MDT 2008 - update deployment point database with CSV Files

I have just rebuilt our deplyment server - before wiping the old server which had bdd 2007 installed - I exported the deploment database repsository to CSV files
So all the information that was stored for Computers, roles, locations. make and models are in CSV files

I have rebuilt the server and installed MDT 2008 which is the new and improved BDD
I have setup everything including the SQLEXPRESS database to store the repository
but there is no option to import the formerly exported CSV files

Is there anyway to do this - either in MDT or in SQL inself?

0
TED_UBB
Asked:
TED_UBB
  • 3
1 Solution
 
JonLambertCommented:
Hi,

I faced this issue awhile back so I've created a script to do the import into BDD 2007/MDT from a BDD 2.5 export.

Edit the User configurable variables at the beggining of the script, as well as the values in the INI file (INI file and import file must be in the same directory as the script).

I haven't used this in a long time, so let me know if you have any issues. (you will have to rename ImportIntoBDD2007 from .txt to VBS, and the BDD2007migration file from .txt to .INI


ImportIntoBDD2007.txt
BDD2007MIGRATION.txt
0
 
TED_UBBAuthor Commented:
Hi,
Does the above script also import all the setting that are included with each entry in the old database - I think they only migrate the names in the CSV
I think the best thing for me to do is to re-image the server with an snapshot of the old BDD 2007 - backup the BDD database - then re-image the server with a snapshot from last week which has the new MDT software installed and restore the database into the the MDT installation
Thanks for your help
Ted
0
 
JonLambertCommented:
Nope it migrates all fields in the CSV .. I've used this script to do two BDD 2.5 to BDD 2007/MDT migrations
0
 
JonLambertCommented:
Upon re-reading the question .. this script ONLY migrateds computer settings, not roles,locations and Make/Model. So my apologies.  This script imports all fields for the computer settings only.

That being said, re-doing the roles, locations and make/model shouldn't take long by hand, as (in all the instances I've seen) they usually don't contain that much data.

However, if you do have a backup, that may be the easiest option.
0

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now