--- Begin Message ---
- From: "Patrick Leathen " <Patrick.Leathen@xxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Fri, 7 Nov 2008 08:47:17 +1300
Wow sorry for the delayed reply, I was not expecting such a quick response and
I sent the email as I was just leaving for the day.
Attached is a quick overview of the steps I have taken to convert the ADM files
with the FullArmour ADMX Migrator, this also includes the error message I
receive after the conversion. This is actually what I had sent FullArmour
months ago but never received a reply.
Thanks for the tip in regards to the SysProSoft tool, I will give this a go
later on today or over the weekend.
Thanks,
Patrick Leathen
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx on behalf of Scott Klassen
Sent: Fri 7/11/2008 6:56 a.m.
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: MS Office 2003 ADMX Files
The V4 version of the SysProSoft tool can convert ADM directly to ADMX and to
my experience does a better job than the Full Armor software. As an added
bonus, the person behind SysProSoft, Alan Cuthbertson, hangs out on this list.
Scott Klassen
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Cruz, Jerome L
Sent: Thursday, November 06, 2008 10:38 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: MS Office 2003 ADMX Files
All,
Just some thoughts....
When I have run into issues with a direct conversion of an ADM template with
the Full Armor tool, I have had some success by first running an ADM template
through the SysProSoft 'ADM Template Editor' tool
(http://www.sysprosoft.com/products.shtml) and then running the resulting (and
renamed) ADM file through the 'Full Armor' tool. From what I can tell, the
changes are mostly focused on rearrangement of the Strings within the template
though there could easily be others.
That said, I have NOT attempted anything as complex as the Office 2003
templates. One of the issues (nits) I've had in the past with the Office
templates was the lack of any "Explain" tab text. Looking from this at a higher
level, that 'should' make them simpler to covert. On the other hand, you never
know what might set off problems. Perhaps the ADMX formats 'really' want
'Explain' text...and if missing...could generate problems in the converter.
Like I said, just some thoughts...
Jerry Cruz | Group Policies Product Manager | Windows Infrastructure
Architecture | Boeing IT
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Darren Mar-Elia
Sent: Wednesday, November 05, 2008 6:15 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: MS Office 2003 ADMX Files
Patrick-
I haven't tried it but knowing the Full Armor Migrator as I do, I suspect those
ADMs are too complicated or not formatted well for it. What kinds of errors are
you getting?
Darren
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Patrick Leathen
Sent: Wednesday, November 05, 2008 6:07 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] MS Office 2003 ADMX Files
Hi,
I hope I've got this right, first time I'm emailing here...
I just have a quick question, has anybody successfully migrated the Office 2003
ADM files to ADMX? I've attempted this a few times using the FullArmour ADMX
v1.2 tool unsuccessfully and have also posted the question on a few other
forums without receiving any answers, so I thought I'd try my luck here.
Would be great to know if anyone else has attempted this and if they've managed
to successfully convert the files.
Thanks
Patrick Leathen
________________________________
The information contained in this e-mail message is intended only for the use
of the person or entity to whom it is addressed and may contain information
that is CONFIDENTIAL and may be exempt from disclosure under applicable laws.
If you read this message and are not the addressee you are notified that use,
dissemination, distribution, or reproduction of this message is prohibited. If
you have received this message in error, please notify us immediately and
delete the original message. You should scan this message and any attached
files for viruses.
Axon accepts no liability for any loss caused either directly or indirectly by
a virus arising from the use of this message or any attached file.
________________________________
--- End Message ---
