SQL Express deployment problem

  • Thread starter Thread starter Stephen Bashford
  • Start date Start date
S

Stephen Bashford

Please help if you have any thoughts.....

I have an XPe Image with .net 2.0 and SQL Express installed. It all seems
to be working just fine.


However, I'm either having problems ZIPing my image or extracting it onto
the target hardware.

I'm using command line ZIP with the option to recurse & include
system/hidden files. When I extract this onto a clean hard disk my image
works as expected with the applications etc. except SQL Express.

When I start the SQL Server manager it cannot log on using Windows
Authentication. It was working fine before I created the golden image.

Any ideas?

TIA

Stephen
 
Please help if you have any thoughts.....

I have an XPe Image with .net 2.0 and SQL Express installed. It all seems 
to be working just fine.

However, I'm either having problems ZIPing my image or extracting it onto 
the target hardware.

I'm using command line ZIP with the option to recurse & include  
system/hidden files. When I extract this onto a clean hard disk my image  
works as expected with the applications etc. except SQL Express.

When I start the SQL Server manager it cannot log on using Windows  
Authentication. It was working fine before I created the golden image.

Any ideas?

TIA

Stephen
Click to expand...

Hi Stephen

Bad SQL Express 2005 does not support cloning. The product must
be installed on the device post FBreseal phase
http://msdn.microsoft.com/en-us/library/aa940744.aspx#SQLExpress2005Issues

/Steffen
 
We've not had a problem putting SQL exprtess server 2005 on our systems and
cloning them.

Propceed as fiollows.
in Target designer set the reseal phase to 0 (meaning manual re-seal)
Build your target and go through FBA to get the operating system up and
running.
Install and configure your SQL express server
Install anything else you need to have (your application for example)
TEST IT to make sure everything works
Use FBReseal to seal the image
Clone you image to a new disk, we've hed sucess using norton Ghosst and
usimng a disk cloning machine we've never tried zipping end extratcting.
connect your disk to your system and boot.
TEST IT.
 
We've not had a problem putting SQL exprtess server 2005 on our systems
and
cloning them.

Propceed as fiollows.
in Target designer set the reseal phase to 0 (meaning manual re-seal)
Build your target and go through FBA to get the operating system up and
running.
Install and configure your SQL express server
Install anything else you need to have (your application for example)
TEST IT to make sure everything works
Use FBReseal to seal the image
Clone you image to a new disk, we've hed sucess using norton Ghosst and
usimng a disk cloning machine we've never tried zipping end extratcting.
connect your disk to your system and boot.
TEST IT.
Click to expand...

Thanks for the info.

We're not actually cloning or resealing this project.

We didn't want to use Ghost and clone the drive.

However, ImageX does just what we want and it's free.

Cheers,

Stephen
 
Stephen Bashford said:
Thanks for the info.

We're not actually cloning or resealing this project.

We didn't want to use Ghost and clone the drive.

However, ImageX does just what we want and it's free.

Cheers,

Stephen
Click to expand...

I assume you are copying the disk so you can have the same image running on
several machines. It can lead to problems if you do this and put those
machines onto a network (especially if you want them to join a domain)
without the reseal phase.

read the articles here for more information.

http://msdn.microsoft.com/en-us/library/ms932934(WinEmbedded.5).aspx

Basically the Reseal phase resets the systems SID (Security ID) and the
computer name to unique values when the sytem first boots after cloning.

If your machines can never connect to a network (even via a modem) then you
won't have a problem but if they are intended to connect toa network then you
need to seriously think about re-sealing your image before cloning.
 
I assume you are copying the disk so you can have the same image running
on
several machines. It can lead to problems if you do this and put those
machines onto a network (especially if you want them to join a domain)
without the reseal phase.
Click to expand...

Sorry, I should have said that.

Yes, several machines will be produced from that image but not running
Windows Networking so computer name & SID shouldn't be an issue.

Cheers,

Stephen
 
Back
Top