Search results for query: *

Our Access platform, works just fine for some of our smaller customers.

No, we have a a few different versions of our software, the less expensive one uses Access backend, either at the end user location or via hosted on a Terminal Server, which is what we do. I even have blank databases that already have the indexes in place, but get an error when trying to export...

I know it sounds like a dumb thing to do, but we host "live" databases (SQL) and "training" databases (currently SQL). I'm using a perfectly great PowerEdge Server to host "training" databases, which do not get used much, but have to be available for the users, and just do not want to waste...

I have SQL 2005 databases I would like to export to Access to include the indexes. I can export the data successfully using the wizard, but there is no choice to export the indexes. What is the easiest way to complete this task? Thank you.

Thank you for your answer, but I just don't understand, I am not educated in programming, nor advanced SQL things. That just looks like jibberish to me. There is no "quick and easy" way to export indexes from a SQL 2005 database to Access? The database export is simple enough, I wonder why is...

I have SQL 2005 databases I would like to export to Access to include the indexes. I can export the data successfully using the wizard, but there is no choice to export the indexes. How does one complete this task? Thank you.

Well for the most part the Local Security Policy is the same, except for the Terminal Server part (the other 2008 box is not a TS). I have a "System Message" set on the TS2008 box and read that with this set, Vista users will be prompted at the server instead of at the RDC client. I could...

Yeah, I guess that will work.

I setup the 2420 on my test machine via LPT and it works, but don't know if it would make any difference via USB or TCP/IP with the actual printer.

No, that is not the issue. It's only particular to this TS2008 box, It's something in the local security policy, I'm sure, but forgot what setting. My other 2008 box prompts on the end user Vista machine first, as it should.

I just finished re-building a TS 2008 box, and am not sure what setting was set, but prior to the re-build, Vista users were prompted for username and password within the RDC software, prior to actually connecting to the TS box. Since this re-build, Vista users are now prompted at the TS 2008...

Well forget it. For whatever reason, it's working now.

In all of the user's profiles on my Terminal Servers is DRWTSN32.LOG located in C:\Documents and Settings\USER.NAME\Local Settings\Application Data\Microsoft\Dr Watson These log file are anywhere form 2MB-16MB and all old. I have unhidden all files as well as unhidden protected operating system...

Well I found the reg key that needs to be set on the client end. [HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR] "RedirectDefaultPrinterOnly"=dword:1

Issue arose today: Server 2008, in a GPO, I have "Use TS Easy Print Driver first" and "Redirect only the clients default printer". This has been working great for all users that meet the requirments for it to work. I have 1 client, Windows XP sp3 and .NET Framework 3.5...

Thanks, I'll look into it. I'm also rebuilding this 2008 TS from 64BIT to 32BIT, so I have a feeling that the profiles will be smaller. Well they are on my 32BIT 2003 TSs about 400k-800k each.

Any other help with this? I'm still looking for a way to have only the clients default printer redirected in their terminal session. My gpo is set at the user OU level and policies work as specified, except for the defualt printer. This does work in 2008 with the TS East Print, but not 2003 R2.

I actually found out that Microsoft .NET Framework 3.0 sp1 or higher (3.5) must be installed for TS Easy Print to work. I ASSumed it came with SP3, but I was wrong.

Yes I have a GPO to specify this, and Terminal Services Configuration has "Use connection settings from user settings" checked, and of course, it is checked on every user's profile.

If it's from the MSDN, call and let them know you are "testing" and had to reinstall the OS, they will gladly reinstate it.