Autodesk Technology Managers Forum
Share your knowledge, ask questions, and engage with fellow CAD/BIM Managers.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

R2004, roaming profiles, custom content, etc.

17 REPLIES 17
Reply
Message 1 of 18
Anonymous
280 Views, 17 Replies

R2004, roaming profiles, custom content, etc.

So we are getting close to rolling out R2004, and I am curious what other
offices have done with regards to locations of content. We have some
requirements, OK hopes, that suggest making use of the new folder locations,
but some issues still make my head hurt.

1: I want to use roaming profiles, not because people really roam that much,
but because it allows those settings to be easily backed up as they really
live on the server, and rolling out a new or trickle down machine become a
cinch.

2: I use customized standard menus. For example, I have pulled the
lineweight & color pulldowns out of the standard menu. They take up space,
and we are not using lineweights in the DWG, and almost never force a color.
ABsically I applied the Woody Leanard test to the toolbars, and it has
worked well. However, as a custom menu it seems like it should live on the
server, or as part of a roaming profile, but read only. On the other hand, I
don't want to limit users from modifying the standard toolbars for their own
style of working. Or do I creat a custom menu for everyone, that lives in
their roaming profile folder, and maybe has all or some of the standard Acad
toolbars in it for them to tweak. So in the end, they might be using the
office standard modifications of the Standard & Properties toolbars, and
their own tweaks of the Draw & Modify toolbars. But all stored in the
roaming profile? Argh, I just don't know.

3: Shared or local versions of PlotStyles? Right now all the plot styles
live in one shared folder. Has anyone played with copying just the CTBs the
user needs to their roaming profile. The office standard stuff could be
locked down for most users, while other files are available to tweak. If so,
how do they get shared? Maybe there is a network resource by project, and an
automated way to download to the profile? Hmm?

If anyone has some insight on how they are actually using these new features
I would love to hear about it. I know a lot of people have just left things
on the server where they have been for ever, but I am wanting to wring as
much out of the improvements as I can, even if it hurts my brain figuring
out what to do and how.

Best,
Gordon
17 REPLIES 17
Message 2 of 18
Anonymous
in reply to: Anonymous

What's the Woody Leanard test (or wood leanOrd?), I just found an email
newsletter page.

Dan

"Gordon Price" wrote in message
news:8516B7185DF03DD5AA94AB558B6382DF@in.WebX.maYIadrTaRb...

> Basically I applied the Woody Leanard test to the toolbars, and it has
> worked well. However, as a custom menu it seems like it should live on the
Message 3 of 18
Anonymous
in reply to: Anonymous

oops, meant woody leOnard

"Dan Allen" wrote in message
news:A85A1ADC4C413AC8F83063B6E2974F49@in.WebX.maYIadrTaRb...
> What's the Woody Leanard test (or wood leanOrd?), I just found an email
> newsletter page.
>
> Dan
>
> "Gordon Price" wrote in message
> news:8516B7185DF03DD5AA94AB558B6382DF@in.WebX.maYIadrTaRb...
>
> > Basically I applied the Woody Leanard test to the toolbars, and it has
> > worked well. However, as a custom menu it seems like it should live on
the
>
>
>
Message 4 of 18
sue_lundergan
in reply to: Anonymous

You mean Woody Leonhard (author of "Office 97 Annoyances" and other wonderful books).

Just curious - what's the "test" you applied to the toolbars?
Message 5 of 18
Anonymous
in reply to: Anonymous

Yes, it should be Woody Leonhard. His theory is that menus & toolbars are
designed for 'wow, that's cool' demonstrations of the product 'out of the
box' and not for actual day to day use. In his book he goes thru a good
cleaning of the Word toolbars to eliminate tools that are rarely if ever
used, and replace them with things that are missing, but that are used every
day. So in Acad, I ditch the Lineweight & PlotStyle pulldowns that take up
so much space and are not used (in our office right now), then add a close
button, which I actually do use every day, and which Acad doesn't even have
an icon for (huh?) I made my Close button actually do Save & Close, which is
really what I want 99% of the time. I also removed a lot of the zoom
buttons, to promote using the mouse driven versions. I mean, does it really
make any sense to have Pan, Zoom & Zoom Previous, as well as a flyout of
those three and then some. I just leave the flyout and ditch the other
three. Users who won't learn the mouse can put them back, but users who
learn the mouse find it is MUCH faster.
I really wish AutoDesk would put some usability testing to the toolbars, and
create a standard menu & toolbar set that works better for most people, and
have the standard install still place a Demo menu to be loaded to show the
'cool stuff' out of the box. Then again, why doesn't the standard PGP use C
for Copy instead of Circle. I have yet to meet someone who didn't change
that.

Then again, if they did that, I would get paid for doing it, which would
make me sad 😉

Gordon
Message 6 of 18
Anonymous
in reply to: Anonymous

Gordon,

I know exactly what you are trying to do - I've rolled out a system
that separates menus and keeps everything on the server, where it
should be.

Roaming profiles are part of the overall IT equation, but may or may
not enter into the situation here, depending on your preferences. I
don't use them to store any CAD related information like menus, I use
other mechanisms.

The problem with using a roaming profile is that they grow over time
as people add stuff; people may delete a folder under My Documents
without understanding that it might be really important. I treat the
My Documents folder as the user's playground, free to add/delete stuff
to it as they wish, as long as they don't (a) store ANY company
related material that would go in a project or admin folder, and (b)
go over about 150 MB and clog up my server.

The other problem is one of portability and ease of management by the
CAD Manager (that's me). Digging through a \\Server\Profiles share to
fix something in a user's menu is a bit of a pain. And when a user
leaves I have to usually wade through their stuff to make sure there's
no work related info on it. On the user's machine, to effectively use
MyDocs you would need to addd it to the support path - and typing in
"C:\Documents and Settings\[Username]\My Documents\acad\" is a real
pain. Also, since people may have Windows installed on D:\, you have
issues with support path consistency. Add to that the fact that
Windows NT uses the C:\Winnt\Profiles folder instead, and a mixed-OS
environment would have issues dealing with roaming profiles used in
the Acad configuration.

On the server I built a folder system using company folders for common
menus (e.g., ACAD, AECARCHX), and a set of folders that are named
after the users' Window Login Names, and everything pertaining to the
user's AutoCAD stuff uses the same name. So I have a folder structure
like

J:\Users\Matt
\Bob
\RBooth
\GMoore

etc. (some users have 1st initial+last name, some are first name only
- legacy type stuff). I used the user's login names because I can
directly get that through AutoLISP and repeatedly refer to that menu
group easily. It's independent of the computer system, operating
system and AutoCAD version. It's only username dependent.

I could have just used the word "user", but that's kind of impersonal
and there's no way to tie that directly to the user; and there's the
possibility of someone accidentally being configured to use someone
else's menu system.

Under each [username] folder, I have an \Acad folder, and under that
go a stock [Username].mns, [username].mnl file and some custom bitmaps
I made. I edit the MNS so the [username] is the menu group name. The
J:\Users\[UserName]\acad folder is in the AutoCAD support path, near
the top of the list.

This menu is strictly for toolbars and accelerator keys. Mostly
toolbars, because they can be edited through the interface. Being that
the stock ACAD menu is on the server, read only, people cannot make
changes to the ACAD toolbar, but they can easily copy a button to one
of their toolbars and create their own set of toolbars. Most people
here use very few toolbars, but the only ones they do use are their
own.

As far as item 3 is concerned, I put everything that is a company
standard on the server. The local machine is "disposable" in my office
- they can die horrible little deaths for all I care, because I've
made it illegal to store anything of company value on the
workstations. So I have a J:\Plot Styles folder, as well as a
J:\Plotters folder.

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com







On Tue, 24 Jun 2003 13:08:57 -0700, "Gordon Price"
wrote:

>So we are getting close to rolling out R2004, and I am curious what other
>offices have done with regards to locations of content. We have some
>requirements, OK hopes, that suggest making use of the new folder locations,
>but some issues still make my head hurt.
>
>1: I want to use roaming profiles, not because people really roam that much,
>but because it allows those settings to be easily backed up as they really
>live on the server, and rolling out a new or trickle down machine become a
>cinch.
>
>2: I use customized standard menus. For example, I have pulled the
>lineweight & color pulldowns out of the standard menu. They take up space,
>and we are not using lineweights in the DWG, and almost never force a color.
>ABsically I applied the Woody Leanard test to the toolbars, and it has
>worked well. However, as a custom menu it seems like it should live on the
>server, or as part of a roaming profile, but read only. On the other hand, I
>don't want to limit users from modifying the standard toolbars for their own
>style of working. Or do I creat a custom menu for everyone, that lives in
>their roaming profile folder, and maybe has all or some of the standard Acad
>toolbars in it for them to tweak. So in the end, they might be using the
>office standard modifications of the Standard & Properties toolbars, and
>their own tweaks of the Draw & Modify toolbars. But all stored in the
>roaming profile? Argh, I just don't know.
>
>3: Shared or local versions of PlotStyles? Right now all the plot styles
>live in one shared folder. Has anyone played with copying just the CTBs the
>user needs to their roaming profile. The office standard stuff could be
>locked down for most users, while other files are available to tweak. If so,
>how do they get shared? Maybe there is a network resource by project, and an
>automated way to download to the profile? Hmm?
>
>If anyone has some insight on how they are actually using these new features
>I would love to hear about it. I know a lot of people have just left things
>on the server where they have been for ever, but I am wanting to wring as
>much out of the improvements as I can, even if it hurts my brain figuring
>out what to do and how.
>
>Best,
>Gordon
>
Message 7 of 18
Anonymous
in reply to: Anonymous

"Matt Stachoni" wrote in message:
> Gordon,


good info, Matt. Thanks.
I'm setup similar here, on a Client XP, Sever 2000 environment.
One thing to add:
Each user's desktop shortcut icon target has been modified to
use the ":\acad\support\MyProfile.arg" path for the "/p"
switch.
That way the added support paths that are user specific load when acad
is started.
(as well as other user customizations that are stored in the acad
profile)
With roaming profiles, in combination with server-based user
customizations
I can login to a different client,
and get the exact same acad environment.

--
CoreyL
Message 8 of 18
Anonymous
in reply to: Anonymous

I've had problems with using the /p and storing ARG files for users before.
If the network is properly setup, all the ARG file is, is a text document of
the registry settings for the user, so if roaming profiles are being used on
the network, then storing and using ARG files isn't necessary, IMO.

I imagine it all boils down to how anyone chooses to manage their CAD
system. I'm similarly setup to the both of you. I put vanilla CAD on the
machine and that's how I leave it. Once a user has logged in and I setup
their station, I just add our custom menu to their autoload path for
AutoCAD. Once the menu is loaded it loads an MNL file which triggers all
the necessary LISP files and VBA files that will check and adjust project
paths, support paths, menu structure, system variables, etc. These
routines also act as maintenance routines. Should a support path ever
change, I simply change it in one location, then the next time/day a user
logins after that change, their paths/menus/etc. are changed appropriately
without them really ever knowing.

I don't have many users that are savvy enough to worry about user menus or
mess-ups with the AutoCAD menu, but I do have a routine that will load a
user menu if they create it in their user path on the network, similar to
what Matt does.

On the company standards side of things, there is a network drive share (
H:\ in my case) that is dedicated to company standards. It's read only to
the average user, it stores blocks/plot styles/pen
styles/drivers/fonts/templates/etc.


"Corey A. Layton" wrote in message
news:A2FD58BB33F1AA1261EA334850088900@in.WebX.maYIadrTaRb...
> "Matt Stachoni" wrote in message:
> > Gordon,
>
>
> good info, Matt. Thanks.
> I'm setup similar here, on a Client XP, Sever 2000 environment.
> One thing to add:
> Each user's desktop shortcut icon target has been modified to
> use the ":\acad\support\MyProfile.arg" path for the "/p"
> switch.
> That way the added support paths that are user specific load when acad
> is started.
> (as well as other user customizations that are stored in the acad
> profile)
> With roaming profiles, in combination with server-based user
> customizations
> I can login to a different client,
> and get the exact same acad environment.
>
> --
> CoreyL
>
>
>
Message 9 of 18
Anonymous
in reply to: Anonymous

This got me thinking....
My company does not use roaming profiles. I am the cad manager
not the it department so I cannot get them to switch, but If I was doing
it all myself I would use roaming profiles.

But I was thinking, what if roaming profiles were used, but the
my documents and the custom autocad stuff stayed on the server.
If the "My Documents" directory was redirected to be on the server
then that would seriously cut down of files being transfered during login/logoff.
Also you could put a quota on each users server space to limit the
my documents size. The use AD to move the temp and net cash out of
the profile onto the local machine. That should seriously cut down
the issues with running roaming profiles. If of course there was a
standard OS.

Matt

What happens with roaming profiles if you have a 2000 profile and then
log into an XP mahine and then go back to a 2000? Is the profile compatable
with both releases? Then what about office 2k and xp?

dave

Matt Stachoni
|>I know exactly what you are trying to do - I've rolled out a system
|>that separates menus and keeps everything on the server, where it
|>should be.
|>
|>Roaming profiles are part of the overall IT equation, but may or may
|>not enter into the situation here, depending on your preferences. I
|>don't use them to store any CAD related information like menus, I use
|>other mechanisms.
|>
|>The problem with using a roaming profile is that they grow over time
|>as people add stuff; people may delete a folder under My Documents
|>without understanding that it might be really important. I treat the
|>My Documents folder as the user's playground, free to add/delete stuff
|>to it as they wish, as long as they don't (a) store ANY company
|>related material that would go in a project or admin folder, and (b)
|>go over about 150 MB and clog up my server.
|>
|>The other problem is one of portability and ease of management by the
|>CAD Manager (that's me). Digging through a \\Server\Profiles share to
|>fix something in a user's menu is a bit of a pain. And when a user
|>leaves I have to usually wade through their stuff to make sure there's
|>no work related info on it. On the user's machine, to effectively use
|>MyDocs you would need to addd it to the support path - and typing in
|>"C:\Documents and Settings\[Username]\My Documents\acad\" is a real
|>pain. Also, since people may have Windows installed on D:\, you have
|>issues with support path consistency. Add to that the fact that
|>Windows NT uses the C:\Winnt\Profiles folder instead, and a mixed-OS
|>environment would have issues dealing with roaming profiles used in
|>the Acad configuration.
|>
|>On the server I built a folder system using company folders for common
|>menus (e.g., ACAD, AECARCHX), and a set of folders that are named
|>after the users' Window Login Names, and everything pertaining to the
|>user's AutoCAD stuff uses the same name. So I have a folder structure
|>like
|>
|>J:\Users\Matt
|> \Bob
|> \RBooth
|> \GMoore
|>
|>etc. (some users have 1st initial+last name, some are first name only
|>- legacy type stuff). I used the user's login names because I can
|>directly get that through AutoLISP and repeatedly refer to that menu
|>group easily. It's independent of the computer system, operating
|>system and AutoCAD version. It's only username dependent.
|>
|>I could have just used the word "user", but that's kind of impersonal
|>and there's no way to tie that directly to the user; and there's the
|>possibility of someone accidentally being configured to use someone
|>else's menu system.
|>
|>Under each [username] folder, I have an \Acad folder, and under that
|>go a stock [Username].mns, [username].mnl file and some custom bitmaps
|>I made. I edit the MNS so the [username] is the menu group name. The
|>J:\Users\[UserName]\acad folder is in the AutoCAD support path, near
|>the top of the list.
|>
|>This menu is strictly for toolbars and accelerator keys. Mostly
|>toolbars, because they can be edited through the interface. Being that
|>the stock ACAD menu is on the server, read only, people cannot make
|>changes to the ACAD toolbar, but they can easily copy a button to one
|>of their toolbars and create their own set of toolbars. Most people
|>here use very few toolbars, but the only ones they do use are their
|>own.
|>
|>As far as item 3 is concerned, I put everything that is a company
|>standard on the server. The local machine is "disposable" in my office
|>- they can die horrible little deaths for all I care, because I've
|>made it illegal to store anything of company value on the
|>workstations. So I have a J:\Plot Styles folder, as well as a
|>J:\Plotters folder.
Message 10 of 18
Anonymous
in reply to: Anonymous

"Dave Lewis" wrote in message
news:k6ijfvckjnapfnbvtjjme6ql3r9p5i7h54@4ax.com...
> This got me thinking....
> My company does not use roaming profiles. I am the cad manager
> not the it department so I cannot get them to switch, but If I was doing
> it all myself I would use roaming profiles.
>
> But I was thinking, what if roaming profiles were used, but the
> my documents and the custom autocad stuff stayed on the server.
> If the "My Documents" directory was redirected to be on the server
> then that would seriously cut down of files being transfered during
login/logoff.
> Also you could put a quota on each users server space to limit the
> my documents size. The use AD to move the temp and net cash out of
> the profile onto the local machine. That should seriously cut down
> the issues with running roaming profiles. If of course there was a
> standard OS.

That is pretty much what we are doing. My Docs & Desktop are server
locations. Profiles roam. All machines have a single HD so no issues of Acad
installed on 😧 in some cases. All WinXP Pro. We really are lucky to have
such a clean setup that we can consider some things that other realistically
can't. I am not sure how much of this stuff can be made useful now, but I
sure want to pick everyone's brain about what walls they banged their heads
on, then go on to bang my head on new and un-banged walls.

Gordon
Message 11 of 18
Anonymous
in reply to: Anonymous

Gordon

Would you send me the code(language) you use to create the save and
close button.

Thanks

Gordon Price wrote:
>
> Yes, it should be Woody Leonhard. His theory is that menus & toolbars are
> designed for 'wow, that's cool' demonstrations of the product 'out of the
> box' and not for actual day to day use. In his book he goes thru a good
> cleaning of the Word toolbars to eliminate tools that are rarely if ever
> used, and replace them with things that are missing, but that are used every
> day. So in Acad, I ditch the Lineweight & PlotStyle pulldowns that take up
> so much space and are not used (in our office right now), then add a close
> button, which I actually do use every day, and which Acad doesn't even have
> an icon for (huh?) I made my Close button actually do Save & Close, which is
> really what I want 99% of the time. I also removed a lot of the zoom
> buttons, to promote using the mouse driven versions. I mean, does it really
> make any sense to have Pan, Zoom & Zoom Previous, as well as a flyout of
> those three and then some. I just leave the flyout and ditch the other
> three. Users who won't learn the mouse can put them back, but users who
> learn the mouse find it is MUCH faster.
> I really wish AutoDesk would put some usability testing to the toolbars, and
> create a standard menu & toolbar set that works better for most people, and
> have the standard install still place a Demo menu to be loaded to show the
> 'cool stuff' out of the box. Then again, why doesn't the standard PGP use C
> for Copy instead of Circle. I have yet to meet someone who didn't change
> that.
>
> Then again, if they did that, I would get paid for doing it, which would
> make me sad 😉
>
> Gordon
Message 12 of 18
Anonymous
in reply to: Anonymous

Corey,

The problems I had with using the /p switch across multiple users is
that many of the profile's path settings are tuned to the user's TEMP
folder, which is different depending on what OS you might be using
(e.g., NT4 vs Win2K or WinXP). So creating a single ARG file and
importing that didn't work.

I ultimately went with a completely hand written VisualLISP
application which reads in an INI file that sets all of the registry
settings and Preferences all at one time.

That way I can change the back end file system, and run the app at
each user's station (automated through the company via a centralized
acad.lsp file) to make the required updates automatically..

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com




On Wed, 25 Jun 2003 06:12:34 -0700, "Corey A. Layton"
wrote:

>"Matt Stachoni" wrote in message:
>> Gordon,
>
>
>good info, Matt. Thanks.
>I'm setup similar here, on a Client XP, Sever 2000 environment.
>One thing to add:
>Each user's desktop shortcut icon target has been modified to
>use the ":\acad\support\MyProfile.arg" path for the "/p"
>switch.
>That way the added support paths that are user specific load when acad
>is started.
>(as well as other user customizations that are stored in the acad
>profile)
>With roaming profiles, in combination with server-based user
>customizations
>I can login to a different client,
>and get the exact same acad environment.
Message 13 of 18
Anonymous
in reply to: Anonymous

Dave,

As far as roaming profiles themselves are concerned, I posted my
favorable feelings about them. my network is completely roaming with
excellent results.

However, from what I've been able to test out over the past four years
of running Win2K Server and Win2K + workstations, I cannot seem to see
where roaming profiles and AutoCAD configurations can meld seamlessly.
There's always something about how AutoCAD works at the Registry level
that precludes using the users' Windows profile effectively.

I believe AutoCAD 2004 is much more roaming profile friendly - perhaps
too much so.

For a while I tested having the My Documents folder server-side only,
but it was quirky in normal everyday use. Nothing bad, but performance
was definitely slower and sometimes things (explorer.exe) just got
stuck. So I bagged it.

While I could store users' AutoCAD info in the Windows profile - even
through My Documents and use Group Policy to ensure that the folder
stays in the server - I didn't see how that was any better than using
a central storage location (e.g., J:\Users\...) for user centric
AutoCAD related storage. It just made the system more difficult to
control, because I can easily navigate a single folder tree to make
changes to user's menus as required. To do this if everything is
inside a user profile is the ultimate in pain.

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com


On Wed, 25 Jun 2003 09:13:54 -0700, Dave Lewis wrote:

>This got me thinking....
>My company does not use roaming profiles. I am the cad manager
>not the it department so I cannot get them to switch, but If I was doing
>it all myself I would use roaming profiles.
>
>But I was thinking, what if roaming profiles were used, but the
>my documents and the custom autocad stuff stayed on the server.
>If the "My Documents" directory was redirected to be on the server
>then that would seriously cut down of files being transfered during login/logoff.
>Also you could put a quota on each users server space to limit the
>my documents size. The use AD to move the temp and net cash out of
>the profile onto the local machine. That should seriously cut down
>the issues with running roaming profiles. If of course there was a
>standard OS.
>
>Matt
>
>What happens with roaming profiles if you have a 2000 profile and then
>log into an XP mahine and then go back to a 2000? Is the profile compatable
>with both releases? Then what about office 2k and xp?
>
>dave
>
>Matt Stachoni
>|>I know exactly what you are trying to do - I've rolled out a system
>|>that separates menus and keeps everything on the server, where it
>|>should be.
>|>
>|>Roaming profiles are part of the overall IT equation, but may or may
>|>not enter into the situation here, depending on your preferences. I
>|>don't use them to store any CAD related information like menus, I use
>|>other mechanisms.
>|>
>|>The problem with using a roaming profile is that they grow over time
>|>as people add stuff; people may delete a folder under My Documents
>|>without understanding that it might be really important. I treat the
>|>My Documents folder as the user's playground, free to add/delete stuff
>|>to it as they wish, as long as they don't (a) store ANY company
>|>related material that would go in a project or admin folder, and (b)
>|>go over about 150 MB and clog up my server.
>|>
>|>The other problem is one of portability and ease of management by the
>|>CAD Manager (that's me). Digging through a \\Server\Profiles share to
>|>fix something in a user's menu is a bit of a pain. And when a user
>|>leaves I have to usually wade through their stuff to make sure there's
>|>no work related info on it. On the user's machine, to effectively use
>|>MyDocs you would need to addd it to the support path - and typing in
>|>"C:\Documents and Settings\[Username]\My Documents\acad\" is a real
>|>pain. Also, since people may have Windows installed on D:\, you have
>|>issues with support path consistency. Add to that the fact that
>|>Windows NT uses the C:\Winnt\Profiles folder instead, and a mixed-OS
>|>environment would have issues dealing with roaming profiles used in
>|>the Acad configuration.
>|>
>|>On the server I built a folder system using company folders for common
>|>menus (e.g., ACAD, AECARCHX), and a set of folders that are named
>|>after the users' Window Login Names, and everything pertaining to the
>|>user's AutoCAD stuff uses the same name. So I have a folder structure
>|>like
>|>
>|>J:\Users\Matt
>|> \Bob
>|> \RBooth
>|> \GMoore
>|>
>|>etc. (some users have 1st initial+last name, some are first name only
>|>- legacy type stuff). I used the user's login names because I can
>|>directly get that through AutoLISP and repeatedly refer to that menu
>|>group easily. It's independent of the computer system, operating
>|>system and AutoCAD version. It's only username dependent.
>|>
>|>I could have just used the word "user", but that's kind of impersonal
>|>and there's no way to tie that directly to the user; and there's the
>|>possibility of someone accidentally being configured to use someone
>|>else's menu system.
>|>
>|>Under each [username] folder, I have an \Acad folder, and under that
>|>go a stock [Username].mns, [username].mnl file and some custom bitmaps
>|>I made. I edit the MNS so the [username] is the menu group name. The
>|>J:\Users\[UserName]\acad folder is in the AutoCAD support path, near
>|>the top of the list.
>|>
>|>This menu is strictly for toolbars and accelerator keys. Mostly
>|>toolbars, because they can be edited through the interface. Being that
>|>the stock ACAD menu is on the server, read only, people cannot make
>|>changes to the ACAD toolbar, but they can easily copy a button to one
>|>of their toolbars and create their own set of toolbars. Most people
>|>here use very few toolbars, but the only ones they do use are their
>|>own.
>|>
>|>As far as item 3 is concerned, I put everything that is a company
>|>standard on the server. The local machine is "disposable" in my office
>|>- they can die horrible little deaths for all I care, because I've
>|>made it illegal to store anything of company value on the
>|>workstations. So I have a J:\Plot Styles folder, as well as a
>|>J:\Plotters folder.
Message 14 of 18
Anonymous
in reply to: Anonymous

I have not implemented roaming network profiles but I have put shareable
AutoCAD content on the server and adjusted AutoCAD options accordingly -
plotters, plot styles, templates, drivers (a networked HDI printer for our
KIP - no need to install on every CAD PC), also just stating to get ADT
content on server.

For plot styles, I have a read only folder for company standard settings
with a shortcut to the user folder i.e. e.g. H:\\A2004\plotstyles
(H: is mapped to the user at login) The user can then add their own plot
styles to the H: path and still be seen by AutoCAD.

AutoCAD Profiles have changed in A2004, ARG files are not used directly -
profile.aws is where profile info is found and for each user in the
following location: (all my AutoCAD stations are now on Win XP Pro)

C:\Documents and Settings\\Application Data\Autodesk\Autodesk
Architectural Desktop 2004\R16.0\enu\Support\Profiles\

*.ARG's are used for export/import only.

So, for now each user will save a *.ARG that they can apply if they use
another CAD station. It's not pretty but will work.

Getting one's head around Win XP compliance makes life very difficult at
times.

If I implement roaming profiles, I will at least get the desktops
automatically transportable but will still need to import the *.ARG file.

--
Darren Myles
CAD Manager
Loughnan Hall & Thompson
Hastings, New Zealand

"Gordon Price" wrote in message
news:8516B7185DF03DD5AA94AB558B6382DF@in.WebX.maYIadrTaRb...
> So we are getting close to rolling out R2004, and I am curious what other
> offices have done with regards to locations of content. We have some
> requirements, OK hopes, that suggest making use of the new folder
locations,
> but some issues still make my head hurt.
>
> 1: I want to use roaming profiles, not because people really roam that
much,
> but because it allows those settings to be easily backed up as they really
> live on the server, and rolling out a new or trickle down machine become a
> cinch.
>
> 2: I use customized standard menus. For example, I have pulled the
> lineweight & color pulldowns out of the standard menu. They take up space,
> and we are not using lineweights in the DWG, and almost never force a
color.
> ABsically I applied the Woody Leanard test to the toolbars, and it has
> worked well. However, as a custom menu it seems like it should live on the
> server, or as part of a roaming profile, but read only. On the other hand,
I
> don't want to limit users from modifying the standard toolbars for their
own
> style of working. Or do I creat a custom menu for everyone, that lives in
> their roaming profile folder, and maybe has all or some of the standard
Acad
> toolbars in it for them to tweak. So in the end, they might be using the
> office standard modifications of the Standard & Properties toolbars, and
> their own tweaks of the Draw & Modify toolbars. But all stored in the
> roaming profile? Argh, I just don't know.
>
> 3: Shared or local versions of PlotStyles? Right now all the plot styles
> live in one shared folder. Has anyone played with copying just the CTBs
the
> user needs to their roaming profile. The office standard stuff could be
> locked down for most users, while other files are available to tweak. If
so,
> how do they get shared? Maybe there is a network resource by project, and
an
> automated way to download to the profile? Hmm?
>
> If anyone has some insight on how they are actually using these new
features
> I would love to hear about it. I know a lot of people have just left
things
> on the server where they have been for ever, but I am wanting to wring as
> much out of the improvements as I can, even if it hurts my brain figuring
> out what to do and how.
>
> Best,
> Gordon
>
>
Message 15 of 18
Anonymous
in reply to: Anonymous

Has anyone addressed this issue with 2004 and roaming profiles?

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=3277956&linkID=2475161
Message 16 of 18
Anonymous
in reply to: Anonymous

I've run into this bug and after applying the suggested solution everything
is fine

--
Best Regards, Jimmy B
CAD and Database Developer Manager at www.pharmadule-emtunga.com
Take a look at the trial version of SmartPurger (now for AutoCAD 2004) or
download some freeware at www.jtbworld.com
More on AutoCAD 2004;
www.jtbworld.com/autocad2004.htm
www.jtbworld.com/autocad2004tips.htm


"Andrew W. Schmidt" wrote in message
news:2EB85827D30306F591495900678D8472@in.WebX.maYIadrTaRb...
> Has anyone addressed this issue with 2004 and roaming profiles?
>
>
http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=3277956&lin
kID=2475161
>
>
Message 17 of 18
Anonymous
in reply to: Anonymous

On Wed, 2 Jul 2003 17:05:16 -0700, "Darren Myles"
wrote:

>If I implement roaming profiles, I will at least get the desktops
>automatically transportable but will still need to import the *.ARG file.

Darren,

It may be possible to use Windows environment variables in the AutoCAD
shortcut using the /p switch after the acad.exe, so that you will
import the ARG file automatically because it gets copied with the
profile data [As of yet untested by me in A2K4]

For example, if you set up ARG files to reside in the user's My
Documents folder, you can have a shortcut that as this as its target:

"C:\[AutoCAD path]\acad.exe" /p "%USERPROFILE%\My
Documents\Acad\%USERNAME%.arg"

If you do a SET command at the console, you get a full list of
envirnment variables that are available, so it's easy to tie a profile
to a user.

Matt
mstachoni@comcast.net
mstachoni@bhhtait.com
Message 18 of 18
Anonymous
in reply to: Anonymous

Tried that - /p doesn't like ARG files in A2k4. The profile needs loading
from one stored in the AWS file. ARG's are just for backup - i.e. export to
restore later. ARG files still work in A2k.
Darren

"Matt Stachoni" wrote in message
news:4tkpgv0edi9anmnv8qc21rd8b6bc884ej6@4ax.com...
> On Wed, 2 Jul 2003 17:05:16 -0700, "Darren Myles"
> wrote:
>
> >If I implement roaming profiles, I will at least get the desktops
> >automatically transportable but will still need to import the *.ARG file.
>
> Darren,
>
> It may be possible to use Windows environment variables in the AutoCAD
> shortcut using the /p switch after the acad.exe, so that you will
> import the ARG file automatically because it gets copied with the
> profile data [As of yet untested by me in A2K4]
>
> For example, if you set up ARG files to reside in the user's My
> Documents folder, you can have a shortcut that as this as its target:
>
> "C:\[AutoCAD path]\acad.exe" /p "%USERPROFILE%\My
> Documents\Acad\%USERNAME%.arg"
>
> If you do a SET command at the console, you get a full list of
> envirnment variables that are available, so it's easy to tie a profile
> to a user.
>
> Matt
> mstachoni@comcast.net
> mstachoni@bhhtait.com
>
>

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Administrator Productivity


Autodesk Design & Make Report