**
This is not possible to
do on a module by module basis, since the v6 and v7 apps don't even resemble one
another. Here's what I would recommend:
Install ITSM 7 on a dev
or sandbox server, and learn how to configure it. I mean really learn it -
there's a lot more to that in v7. Learn what happens when a user doesn't
have the proper roles and permissions. Learn what happens when the
Assignment engine isn't set up the way you thought it was set up. The list
goes on... There won't be classes in this for another couple months, so
you'll have to figure it out on your own.
When you're ready,
install the apps in the order given in the docs. Note that this is a
different order than in previous versions. Note also that you will have to
have the ITSM application licenses converted prior to actually installing the
apps. You can install ARS, Approval, and the Assignment engine without the
ITSM apps, but that's it. Thankfully, Doug and the crew put a widget on
the support site to convert an existing license file to a v7 one. The
returned .lic file contains both the old ITSM 6 and the new ITSM 7
licenses. You MUST convert them, because the apps aren't even the same
names. Help Desk is now broken down into Incident and Problem Management,
for instance. Also, you didn't use to have actual application licenses at
all - just the application user licenses. v7 requires both, and the
license conversion tool creates those.
Then you have data
migration to think about. The data mapping alone could take weeks.
Some places will actually start over, because it will take less time. It's
up to you to determine if your existing data is worth converting and
migrating.
For these reasons, I
think a forklift deployment strategy (i.e. install and configure the new version
on a new server, and then just deploy that new server in place of the
existing one) is probably the only strategy to upgrade that will combine
a short outage period with a minimal degree of risk. It may be
possible to upgrade some faster way, but I haven't found one yet that doesn't
have major risk factors.
RickFrom: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Den Fong Sent: Wednesday, July 19, 2006 6:58 AM To: arslist@ARSLIST.ORG Subject: ITSM 7 upgrade Hi All
Has anyone gone through this yet? We are looking at putting a plan
together for this upgrade.
We are currently at ARS 6 and ITSM 5.6 (HD/CHG/AST). I know the cmdb
is very important to the whole suite and we will focus on that first and
allotted the most time to it currently. Then we want to move our other
modules on, is it possible to do a module by module basis (AST then HD then
CHG). Or should a cut over be the best solution?
Our current plan is:
CMDB + integration w/Zen 2mths (without EIE)
Asset 6 weeks
ServiceDesk 6 weeks
CHG 6 weeks
This includes examining functionality differences, customization
migrations, and understanding some of the changes in the modules. Does
this sound reasonable? Our higher ups think it's a bit long for an
upgrade.
Thx
Husky Energy Inc. 707-8th Avenue SW Calgary, Alberta CANADA T2P 3G7 Phone : 1-403-298-7244 __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___ |
- ITSM 7 upgrade Den Fong
- Re: ITSM 7 upgrade Rick Cook
- Re: ITSM 7 upgrade Pierson, Shawn
- Re: ITSM 7 upgrade Kelly Deaver
- ARS New Install Kevin Shaffer