Installation & Licensing
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
*Schmidt, Andrew W.
Slow A2K with NT 4.0 and Novell 5.0
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
78 Views, 2 Replies
02-21-2000 12:39 PM
I am experiencing a very interesting problem. We use NT 4.0 and have a
Novell 5.0 Server, with roaming profiles. Until recently, no one really
roamed from machine to machine, so we did not experience any problems. Now
we have hired a few more architects and drafters and we have more people
than we have machines so some of them use a different machine everyday. The
roaming profile worked great to handle this, I was able to setup their
AutoCAD options only once and they would follow the user around to whatever
machine they were logged on. The problem I seem to be experience is as
follows:
Monday: UserA works on machine A, everything is fine. User A logs out and
their profile is copied to the network.
Tuesday: User A works on machine B, their profile (created on Machine A)
is copied down from the network, but when they start AutoCAD it tries to go
back to Machine A to run. I have even made sure I executed the ACAD.EXE
right from within AutoCAD folder, it still tries to go back to machine A. I
looked at the AutoCAD 2000 shortcut on the desktop and sometime (not all the
time) for Target it has \\MACHINE A\c$\R2K\ACAD.EXE (where R2K is our
default location throughout the office) Eventually AutoCAD will start,
(after about 3-4 minutes). I have watched the NT task manager to monitor
the performance while AutoCAD was starting up. It shows AutoCAD 2000 as not
responding, and has the ACAD process listed, but not using any CPU.
My only solution so far is to completely delete the User A profile from both
the local machines and the network and recreate it each time they log onto a
different machine. It appears to me that when User A is logged onto Machine
B, Machine B is using the ACAD.EXE on Machine A. I am also posting with
Novell and Microsoft this same problem in hopes of finding a solution.
Thanks in Advance
Andrew W. Schmidt
CAD Manager
Foreman Architects Engineers
andrew.schmidt@foremangroup.com
Novell 5.0 Server, with roaming profiles. Until recently, no one really
roamed from machine to machine, so we did not experience any problems. Now
we have hired a few more architects and drafters and we have more people
than we have machines so some of them use a different machine everyday. The
roaming profile worked great to handle this, I was able to setup their
AutoCAD options only once and they would follow the user around to whatever
machine they were logged on. The problem I seem to be experience is as
follows:
Monday: UserA works on machine A, everything is fine. User A logs out and
their profile is copied to the network.
Tuesday: User A works on machine B, their profile (created on Machine A)
is copied down from the network, but when they start AutoCAD it tries to go
back to Machine A to run. I have even made sure I executed the ACAD.EXE
right from within AutoCAD folder, it still tries to go back to machine A. I
looked at the AutoCAD 2000 shortcut on the desktop and sometime (not all the
time) for Target it has \\MACHINE A\c$\R2K\ACAD.EXE (where R2K is our
default location throughout the office) Eventually AutoCAD will start,
(after about 3-4 minutes). I have watched the NT task manager to monitor
the performance while AutoCAD was starting up. It shows AutoCAD 2000 as not
responding, and has the ACAD process listed, but not using any CPU.
My only solution so far is to completely delete the User A profile from both
the local machines and the network and recreate it each time they log onto a
different machine. It appears to me that when User A is logged onto Machine
B, Machine B is using the ACAD.EXE on Machine A. I am also posting with
Novell and Microsoft this same problem in hopes of finding a solution.
Thanks in Advance
Andrew W. Schmidt
CAD Manager
Foreman Architects Engineers
andrew.schmidt@foremangroup.com
*Gilmer, Tom
Re: Slow A2K with NT 4.0 and Novell 5.0
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
02-21-2000 04:29 PM in reply to:
*Schmidt, Andrew W.
<<< Message <88sb3g$rvh11@adesknews2.autodesk.com> was originally posted to 'autodesk.autocad.customization.vba' on Mon, 21 Feb 2000 16:33:15 -0500.>>>
Frank,
Sure do!! Below is an excerpt from the Documentation - Tom
Location profiles allow a workstation or network administrator to save
the information from a user's specific login into a location
profile. When the user selects this profile when logging in, the profile
automatically sets up login information such as the user's
name, server, tree, context, login script, and other applicable
information so that the user does not have to type this information.
Location profiles are especially powerful for those users who log in
from multiple places. Users can have separate profiles for the
office, home, the laptop they use when they travel, and any other
workstation they use. This simplifies the login process and makes
it so users do not have to remember their login information for each
workstation. Using multiple location profiles also gives the
network administrator control over what users can access from each
workstation.
Frank Oquendo wrote in message
news:88s87c$rvt9@adesknews2.autodesk.com...
> Are you saying that Novell 5 supports roaming profiles for NT
workstations?
>
> --
> Visit me at: http://www2.stonemedia.com/franko
>
>
Frank,
Sure do!! Below is an excerpt from the Documentation - Tom
Location profiles allow a workstation or network administrator to save
the information from a user's specific login into a location
profile. When the user selects this profile when logging in, the profile
automatically sets up login information such as the user's
name, server, tree, context, login script, and other applicable
information so that the user does not have to type this information.
Location profiles are especially powerful for those users who log in
from multiple places. Users can have separate profiles for the
office, home, the laptop they use when they travel, and any other
workstation they use. This simplifies the login process and makes
it so users do not have to remember their login information for each
workstation. Using multiple location profiles also gives the
network administrator control over what users can access from each
workstation.
Frank Oquendo
news:88s87c$rvt9@adesknews2.autodesk.com...
> Are you saying that Novell 5 supports roaming profiles for NT
workstations?
>
> --
> Visit me at: http://www2.stonemedia.com/franko
>
>
*Oquendo, Frank
Re: Slow A2K with NT 4.0 and Novell 5.0
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
02-21-2000 04:29 PM in reply to:
*Schmidt, Andrew W.
<<< Message <88s87c$rvt9@adesknews2.autodesk.com> was originally posted to 'autodesk.autocad.customization.vba' on Mon, 21 Feb 2000 14:48:57 -0600.>>>
Are you saying that Novell 5 supports roaming profiles for NT workstations?
--
Visit me at: http://www2.stonemedia.com/franko
Are you saying that Novell 5 supports roaming profiles for NT workstations?
--
Visit me at: http://www2.stonemedia.com/franko

