Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Migration from virtual pc to stage server

  Asked By: Ojas    Date: Jun 08    Category: Sharepoint    Views: 875

We are using virtual pc's for develeopment on or local machines. I
have been task to create a tasking workflow system that will have
probably 4+ list and designer workflow behind it. How would i go about
migrating off my virtual pc and move to test then production. I am new
to this process and I do not think it was talked about in the mindsharp
designer course. If anyone knows of a website or web cast this has a
good example of a tasking workflow using sharepoint and designer it
would be of great help.



16 Answers Found

Answer #1    Answered By: Moshe Harding     Answered On: Jun 08

If you are building the workflows using SPD then they are tied to the GUIDs of
the list  where you built them in the dev environment and cannot be moved. You
will need to re-build them in Production. If you look back at your courseware
you will find that this is one of the limitations of SPD workflows that was
mentioned prominently in the Designer course.

Answer #2    Answered By: Carly Meyer     Answered On: Jun 08

So there is no way to do this, so if i go from virtual  pc to a test
box then to a stage box then finaly to a production  box. I am going
to have to recreate the all the list  and re-do the entire workflow  in
sharepoint designer  for each.

Answer #3    Answered By: Dewayne Clay     Answered On: Jun 08

The list  itself can be moved using either Content Deployment or STSADM.exe
Backup or Export. Its just the SPD workflows that can't be moved. SPD is more
of an end user tool in Microsoft's view and they expect it to be used in
Production not Development.

Answer #4    Answered By: Angelina Newman     Answered On: Jun 08

So just to understand correctly, i can move  the 4+ list(doc library,
task, custom list  over), but If i have a 5+ step workfow that
email's, logs, changes list values, etc. I am going to have to re-
create that in every environment. So what is a work around. I am
going to tell my boss we are going to have to re-do the workflow  in
SPD for each enivronment.

Answer #5    Answered By: Shannon Fleming     Answered On: Jun 08

The workaround would be to write the workflow  in Visual Studio. It's the right
tool to use to create  workflows that will be replicated in multiple places.

Answer #6    Answered By: Aditi Msc     Answered On: Jun 08

I have found several web  cast from microsoft, that show if you create
a document review process  with several list  and a spd workflow
process you can save the site as a template and then it can be reused
accross site collections and even on different servers. So would this
solve my problem instaed of having to re-do the workflow  on each

Answer #7    Answered By: Abinav Basu     Answered On: Jun 08

Can you direct me to the web  cast, because this will not work. If you save a
site as a template with an SPD workflow  in place the workflow will be
non-functional in a new site when you create  it. You can then re-edit the
workflow in SPD and fix all the references, but that's about as difficult as
creating it from scratch.

Answer #8    Answered By: Teresa Simpson     Answered On: Jun 08

- it should be the number 14 video.

Answer #9    Answered By: Robby Barr     Answered On: Jun 08

I just dropped a note to the original author of these videos at
Microsoft. He confirmed that using site template (stp) is both a
functional and supported way (the only supported way in fact) to make
SPD workflows portable. This method is used by the "Fantastic Forty"

Answer #10    Answered By: Patrick Davis     Answered On: Jun 08

I hate to disagree with him, but I've tested it and it doesn't work unless you
re-open the workflows in the site after using the site template to create  the
site and re-edit them. SharePoint Designer Workflows are not transportable
without a fair amount of re-work.

Answer #11    Answered By: Alexander Rocha     Answered On: Jun 08

To add to both points. I have sucessfully migrated SPD workflows with
site templates, HOWEVER, only with simple ones and only when the existing site
had minimal customizations. Once I threw in sites that utilized custom content
types, and other non development customizations site templates worked only
occasionally. NOt that it happens right now, but this is one of the reasons I
strongly advocate slinging custom workflow  in Visual Studio 2008 whenever it is
feasible to do so. They are much more flexible, portable, and deployable than
anything the SPDs can throw out. VS 2008 makes is much easier to create  these.
Still need a developer to do it though.

Answer #12    Answered By: Maggie Benson     Answered On: Jun 08

What I forgot to add from the conversation - there are some post-site
creation tweaks that are sometimes necessary and there is a KB article
coming that spell out the details on that. Believe me, I was skeptical
when I got that answer as well, but it does appear to be an official

Answer #13    Answered By: Lane Trujillo     Answered On: Jun 08

Sorry, I'm sticking with Micheal. In my experience the post-site creation
tweaks aren't "sometimes necessary" they are always necessary and they don't
always work.

Answer #14    Answered By: Rafael Willis     Answered On: Jun 08

I did content deployment of a site and SPD workflows were not working.
I opened the site in SharePoint designer  and saw workflow  was there
and opened it and just clicked finish and this process  hydrates
workflow and then it started working.

Another way is stsadm-backup/restore will port SPD workflows and they
will work straight away.

Answer #15    Answered By: Richard Davis     Answered On: Jun 08

I've managed this by copying the files (the xoml is the most important one)
and then doing a Find/Replace on the GUIDs. The workflow  runs as expected
and you can store it in the source control repository of your choice.

Answer #16    Answered By: Mason Davis     Answered On: Jun 08

No sure what you mean, it is getting beyond my head :) from the video
it appears you do not have to do that, you may have to go back into
the workflow  and change hardcoded url references though.

Didn't find what you were looking for? Find more on Migration from virtual pc to stage server Or get search suggestion and latest updates.