D
DCarmody
I recently conducted a domain migration for a client of mine, and I've been
having some issues with Office 2000 documents taking 30 seconds to open ever
since. As part of the migration I moved all the print queues from a server
in the old domain to a server in the new domain. The queues currently exist
on both servers, but the users are connecting to the queues in the new domain
using different naming conventions. There is also a trust relationship
between the old domain and the new domain. The problem is as follows:
When users open an Office document, the SPOOLSV.EXE hovers around 50% CPU
Utilization for about 30 seconds before the document opens. This was not the
case before the migration, so I'm a bit baffled about what is causing this
issue. The only thing I can figure is that the Office application is
attempting to format the document using the print driver from the old print
queue and timing out maybe? Any ideas?
Thanks,
Dan Carmody
Senior Systems Engineer
FCS Consulting Services
having some issues with Office 2000 documents taking 30 seconds to open ever
since. As part of the migration I moved all the print queues from a server
in the old domain to a server in the new domain. The queues currently exist
on both servers, but the users are connecting to the queues in the new domain
using different naming conventions. There is also a trust relationship
between the old domain and the new domain. The problem is as follows:
When users open an Office document, the SPOOLSV.EXE hovers around 50% CPU
Utilization for about 30 seconds before the document opens. This was not the
case before the migration, so I'm a bit baffled about what is causing this
issue. The only thing I can figure is that the Office application is
attempting to format the document using the print driver from the old print
queue and timing out maybe? Any ideas?
Thanks,
Dan Carmody
Senior Systems Engineer
FCS Consulting Services