I'm trying to get EasyPrint to work from workstations running Windows Server
2003, connecting to a Server 2008 TS pool.
I noticed that there is a RDP 6.1 client for XP clients. I couldn't get that
to install on the Server 2003 box.
I was able to install RDP 6.0 client for Server 2003. However it appears
EasyPrint isn't actually working in this case, as we are seeing that printers
without local drivers are not being redirected to the remote desktop.
Information on the web on this topic is somewhat conflicting. Is what we
are trying possible? If yes. Any suggestions on how to get it to work
from a client on a Server 2003 workstation?
http://www.pubforum.info/welcome/BLOG/tabid/78/EntryID/6/Default.aspx
This will do is for you :-)
Kim
Terminal Server Easy Print Overview:
http://winplat.net/post/Terminal-Server-Easy-Print-Overview.aspx
Installing the XP version of 6.1 will work for 32-bit Server 2003, but it doesn't work for 64-bit versions of Windows 2003.
Related
I have created program using MSVC++ that besides it's main task calls WCF server functions. Under Windows 7 and Windows 8 everything works fine and I got several problems with Windows XP:
On some machines I have error that webservice.dll is missing and program doesn't starts. Why some Windows XP installations contain webservice.dll while others - not? How to install required dll?
On Win XP computers that has webservice.dll sometimes programm just crashes without any reporting. After recompiling program without WCF client code program runs fine. What might be starting point to look for the problem?
Windows Web Services API (WWSAPI) is an operating-system component of Windows 7 and Windows Server 2008 R2 or later versions of Microsoft Windows.
On Windows XP you need to package it with your app. The reason it works on some boxes is probably caused by one other installed application that uses that the WWSAPI as well.
The final version of the Windows Web Services API for Windows XP, Windows Vista, Windows Server 2003 and Windows Server 2008 is now available
In contrast to the past pre-released version of this API, this final version release can be used in production code and redistributed with the final versions of the product. Because of this, the final version is only available to companies who agree to terms of Windows Master Redistribution License Agreement (MRLA). To acquire the redistributable installers for this release and a copy of the Windows MRLA for review, please email a formal request.
Partially copied and adapted from Windows Core Networking blog, from Ari Pernick, dated Oct 9th, 2009.
I am using 2 machines.
Windows server 2003 with SQL Server 2005 (default instance) MySrvName" and with SQL Server 2000 (named instance) MySrvName\SQL2000
Windows 7 with VS 2010
LAN (works fine)
When I connect to SQL Server 2005 it works fine from win7 and win 2003 but when I try to connect to SQL Server 2000 via win7 it says
The server was not found or was not accessible
This instance (SQL2000) is working fine from Windows server machine. I have tried disabling all firewalls (default of windows).
In 2002-3 I used to have same issue which I used to resolve by installing MSDE/connectivity tools. Is there a way to resolve without installing anything? Or any single file to install these connectivity tools from?
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.
Does anybody know, if it is possible to use the "old" SAP DCOM Connector on a Windows Server 2008 ?
I want to migrate a old ASP Web Solution with DCOM Connection to SAP from Windows 2000 Server to Windows 2008 Server.
When I try to install the DCOM Connector I get the Error Message:
"Setup could not find ActivX(R) Data Objects verion 2.5 or higher on your computer...."
That is strange, because ado is there under C:\Program Files\Common Files\System\ado !
Thanks in advance for your help !
I wasn't able to make it work even on windows 2003 server. I don't remember how hard I tried. But its certainly not supported event for windows 2003. And actually this component is out of support since 2005 or something like this.
I have a windows application that acts as a WCF Service that I developed on a 32bit Windows Server 2008 box. I have tested the application and everything works fine when running it from my development machine, as well as from my 32bit workstation. However, when attempting to run the application on a 64bit Windows 2008 Server, the application does not run, and a Windows Error Report is generated stating that the application stopped working. I have attempted to build the application on my 32bit Development Workstation, targeting both x86 and x64, to no avail. The only time I can get the application to run is if I comment out the code that starts the WCF Service. So my question is, do I need to dev and/or build this application on a 64bit workstation to allow the application to run on a 64bit machine?
Ok, I figured it out, nevermind...needed to run the app as admin on that server...
You need to configure http.sys to accept your urls using the httpcfg utility. There is a similar thing for Windows Server 2003.
How to add a URL ACL and avoid AddressAccessDeniedException in Windows Vista
Httpcfg Examples: Internet Information Services (IIS)