It will. Start the VM with networking disabled the first time. You'll need
to do this anyway so you can adjust the IP and such. You can leave the
original server running.
to do this anyway so you can adjust the IP and such. You can leave the
original server running.
On Tue, May 17, 2011 at 4:30 PM, Brian Roberts <broberts@...> wrote:
>
>
> Thanks for the details. One more question: once the cloned VM is
> started for the first time, isn't the "AdminService for OpenEdge" going
> to start automatically, and start up all the Epicor app servers before
> you have a chance to change the configuration? Do you have to manually
> disable each app server before cloning?
>
>
> Thanks,
>
> Brian.
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Mordechai
> Sent: Tuesday, May 17, 2011 11:27 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Re: Setting up a test server
>
>
> A couple additions
> 1 - fix your system agent to point to the new test server - don't start
> it before you confirm
> 2 - if you plan to use this test box for future upgrades (we do that all
> the time) make sure your .mfgsys in the client directory (on server) and
> in the releaseClient.zip are pointing to the test server and not
> production.
> You will have major issues if you forget that
> Otherwise I would recommend all users that are on VM to clone. It is a
> great timesaver and we never run an upgrade on the production server,
> always rename the upgraded server to the production
>
> Motty
>
> --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
>
> Waffqle <waffqle@...> wrote:
> >
> > No 'official' list that I know of. It's not really too much stuff
> though.
> >
> > Fix before you start Epicor:
> > -Don't dupe your IP.
> > -Don't dupe your machine name.
> > This will take care of potential network issues.
> >
> > Once you set the VM up, you need to square up Epicor and get it happy.
> > -If you have any host entries on the machine, fix them.
> > -Anywhere you have the machine specified by name/IP in your
> Epicor/SC/etc
> > config, fix it.
> > -Fix your system agent.
> >
> > You should be good to go at this point.
> >
> > If you can get away with it, it's much easier/faster to just copy your
> DB
> > instead of replicating the entire server.
> >
> > On Tue, May 17, 2011 at 10:23 AM, Brian Roberts <broberts@...> wrote:
> >
> > >
> > >
> > > The "LOTS of settings need to be updated" bit below caught my eye.
> Is
> > > there a list of these settings, to make sure I don't miss any? We're
> on
> > > a VM, planning to clone the VM to set up a test system.
> > >
> > > Thanks,
> > >
> > > Brian.
> > >
> > > ________________________________
> > >
> > > From: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> [mailto:vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ] On
>
> Behalf
> > > Of too_much_hg
> > > Sent: Monday, May 16, 2011 4:22 PM
> > > To: vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> > > Subject: [Vantage] Re: No Servers Available
> > >
> > > Did you setup a "TEST" Server around the time your problems started
> > > happening ... ?
> > >
> > > Did you do it in a Virtual Environment ?
> > >
> > > Did you do a Physical to Virtual copy and then re-name your TEST
> Server
> > > ? LOTS of settings need to be updated besides ServerName.
> > >
> > > I just wonder if you don't have 2 different Servers trying to access
> > > your Database on the LIVE Server .....
> > >
> > > If you did create a TEST environment around the time your problems
> > > started, try turning that TEST Server OFF for a day and see what
> > > happens.
> > >
> > > Neil
> > >
> > > --- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com>
> <mailto:vantage%40yahoogroups.com> ,
> > > "Ned" <TechnoBabbly@> wrote:
> > >
> > > [Non-text portions of this message have been removed]
>
> [Non-text portions of this message have been removed]
>
>
>
[Non-text portions of this message have been removed]