Enable Local Area Connection in windows server 2008 r2

Hi,
3 Days back i installed the Oracle Virtual box and after installing Ubuntu in it, when i changed the network mode from NAT to bridge, i lost the connectivity with server.
The data center guys has provided a channel in which we can access the server command prompt.
Using this i have removed the following entries from the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxDrv
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetAdp
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetFlt
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VBoxNetUSBMon
but now issue is my network card "Local Area Connection" is not getting enabled and i cant access my server.
How can i enable my Local Area Connection back.
Thanks

Hi
Netsh can do this for you:
netsh interface set interface name="Local Area Connection" admin=enabled
Replace "local area connection" with your connection name.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Similar Messages

8.8 Client cannot connect to Windows Server 2008 error -1102

SAP Business On 8.8 on PL 18
This is not the first time I have had this issue with Windows Server 2008.
however everytime the resolution was diffrent. Now this site is causing trouble.
The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
The client on the Server itself can log on. It is the cleints that cannot.
I checked these below.
1 SQL Native client is installed and ok.
2. Licence server is configured and ok
3. The user has admin access to locl PC
4. The SAP user name and password are correct ( client on server can connect fine )
5. The ports 1433, 30000 and 30001 are open on the server.
6. Through SQL server configuration the named pipes and TCP are enabled.
7. SQL server browser is running
The only things I have not tried are
The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
Do you have any other ideas please ?

I have got this working but I am not confidant of the outcome - yet - I really need your expert advise here.
This is what I did. In that order.
1.     As Owen suggested I checked if there was a specified Port for the instance. What I found was TCP Dynamic ports were enabled ( SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified. Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance I set it up so the Dynamic port does not happen and manually specified the Port 1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now. Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
3.     I had to do the above step for all PCs to get them working.
4. Currently the firewall is on and clients can connect
So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off - to say its safe ?
However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things.
I would still like to get to the bottom of this to understand what is happening.
I have a SAP message running too and will ask them this same question.

Unable to print to local Printer over RDP - Windows Server 2008

Hi,
Windows 2008 Foundation R2.
Started to have issues with printing to a Local printer over RDP.
The problems started on Friday 11th April. The only possible issue I can identify is that around that time LogMeIn was updated on the server, including the LMIPrinter DLL's. I have contacted Logmein for instructions on how to uninstall LMI completely
and followed these but am still experiencing the problem.
When attempting a Test Page print the confirmation that the Test Print has been sent to is displayed and the print appears then disappears in the Print queue but nothing appears on the Local PC print queue or event logs.
On the server the Event Log shows the following error;
The document Test Page, owned by admin, failed to print on printer Canon MG7100 series Printer (redirected 2/copy 1). Try to print the document again, or restart the print spooler.
Data type: RAW. Size of the spool file in bytes: 142691. Number of bytes printed: 0. Total number of pages in the document: 1. Number of pages printed: 0. Client computer: \\ONESTAGE-TS01. Win32 error code returned by the print processor: 2147500037. Unspecified
error
I have searched for possible solutions to RDP printing problems and where relevant implemented them but no change.
I have access to a second customer who uses RDP and am able to log onto that and print to my local printer so am pretty sure there is nothing wrong with the local printer or settings. On the Server with the problem the problem affects all RDP users
and all printers (including Adobe PDF printer and MS XPS printer). All printers are defaulting to the EasyPrint Drivers.
Grasping at straws I think the LMI update has banjaxed something with the RDP remote printing and an LMI uninstall hasn't fixed it. Is there a way to reinstall the RDP Printing? Would uninstalling & reinstalling .NET have that effect?

Hi,
Thank you for posting in Windows Server Forum.
What’s your client OS and RDP version in your environment?
First of all suggest you to run “sfc /scanow” with this link to check whether which file causing the issue. Check the RDP version on the RDP client computer as well as the .NET framework version with respect to the operating system used (as explained above).
Also verify that the RD Session Host / Terminal Server role is installed if the host computer is running Windows Server 2008 R2 or Windows Server 2008.
The setting “Use Remote Desktop Easy Print printer driver first” must be set to “Enabled” for Easy Print redirection, and it has to be “Disabled” for Legacy Print. For “Not configured”, Easy Print is chosen by default.
Check The Remote Desktop Configuration Tool (tsconfig.msc) settings to ensure that the “Windows Printer” option is not disabled (it is not disabled by default).
Make sure that the “Printers” check box in the client (mstsc.exe) window on the “Local Resources” tab is checked. The corresponding setting in the associated RDP file is “redirectprinters:i:1”.
More information:
Using Remote Desktop Easy Print in Windows 7 and Windows Server 2008 R2
http://blogs.msdn.com/b/rds/archive/2009/09/28/using-remote-desktop-easy-print-in-windows-7-and-windows-server-2008-r2.aspx?Redirected=true
Hope it helps!
Thanks.
Dharmesh Solanki

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

How Do i disable ""enable advance Printing features on windows server 2008 ""

Hi ,
I have a windows server 2008 which is used as a terminal server . Users at remote locations log on to this server via "" DYNDNS"" to user our ERP and company files. We use ""DOT MATRIX PRINTERS "" to print . As we all know that ""enable advance
printing feature"" is checked by default on windows server 2008 the format of our ""DOT MATRIX PRINTOUTS "" CHANGE which creates a big mess.
I would like to know if there is any way where i can disable this feature permanently.

In previous operating systems, that setting was for designed for disabling and enabling GDI rendering on the server. Since you are using a TYPE 4 print driver, there is no GDI rendering and thus this setting is not configurable.
If you would like to change this setting, you will need to use a TYPE 3 print driver that does not use XPS rendering. Then the previous configuration methods you were using will work.
Alan Morris Windows Printing Team

Macbook clients cannot connect to Windows Server 2008 RRAS with L2TP/IPSec

Hi everyone,
I had installed "Remote and Routing Access" or a VPN server on Windows Server 2008. The connection type set up is L2TP/IPSec. All the Windows clients can connect to the L2TP/IPSec VPN server without problem but Macbook users are facing problem.
The Macbook users got the error message "The L2TP-VPN server did not respond. Try reconnecting. If the problem continues, verify your settings and contact your Administrator."
I think it is something related to the pre-shared key encryption but I am not sure. The Macbook users could connect if the connection type is changed to PPTP on server and clients side. I searched for similar problems and solutions online but no luck, I couldn't find solution that helps. I found this is a common problem faced by many macbook users.
Does anyone have a solution or suggestion for this, please? I appreciate all the helps and suggestion given.
Thanks,
CK

Hi,
Thanks for the question, however, this forum is for Remote Desktop Clients related questions.
Regarding the issue, as Windows clients can connect with no problem, I suspect that it is a Mac side issue and I would like to suggest you contact Apple support for help.
Thanks.
Jeremy Wu
TechNet Community Support

Internet connection for Windows Server 2008

I have an HP ProBook 6545b notebook computer which I installed an evaluation copy of Windows Server 2008 on. I'm trying to get internet connectivity to work but as yet, it's not.
I get the message that it can't find a network interface card but even with an Ethernet cable connected, it still won't connect to the internet.
For the background, this is the first time I'm trying this on a home computer being I'm a 2012 graduate of a technical school and I'm re-reading all my computer related textbooks.
The HP notebook I'm using gets the internet connection when I have Windows 7 Professional installed.
Is/are there a driver/drivers needed or a service in 2008 I need to install? If it's a driver, where can I get it?

Hi,
That mean windows server does not recognize your network card, you can try the manufacturer driver, or the best move would be to setup a small virtual machine on your notebook, under a windows 7's OS.
You could use virtualbox, or similar product to achieve the goal.
Thanks
Regards, Philippe
Don't forget to mark as answer or vote as helpful to help identify good information. ( linkedin endorsement never hurt too :o) )
Answer an interesting question ? Create a
wiki article about it!

HP Offiejet Pro 8000 A809 prints carbage when using network connection on Windows Server 2008

We are using HP Offiejet Pro 8000 A809 on our network, and they are installed on a Windows 2008 Server.
But when we are sending a print command it prints only garbage. We've tried different print drivers but without success.
Anyone experience the same problem and have a solution?
Thanks

temporary solution from HP is to use the standard HP Deskjet 990c driver.
it works but i hope they make a proper driver.

Sybase ODBC Connection Issue in Windows Server 2008 R2

Hi ,
We have three sybase odbc connection in Windows Server 2008 R2 server . One connection is not working now, it was working fine before 30 days.
I can ping the server address successfully from BO Server through "dsedit".
i have created the same connection in a diffrent server (Win server 2003),and it is working fine.
Sybase ASE Driver version 3.50.00.10
Please help me to overcome this issue.
Thanks,
Saurabh upadhyay

Hi Saurabh,
The error message you are reporting is telling us that you are using the very old ctlibrary ODBC Driver.
That is pretty much the only way you can get that error.
Run from a command prompt, isql -v that will return a version string. We can then verify the version.
However, the old ODBC driver will function with the newer client.
The old driver would read the sql.ini for the network address, and was also a translation layer between
the client application and the ASE.
Both were eliminated when Sybase released the "Native" ODBC Driver.
The ct_connect error states that the connection attempt is using ctlibrary.
In your ODBC configuration, Check to see in the ODBC Administrator and check to make
sure that the driver you are using for your DSN is the Adaptive Server Enterprise and not the
Sybase ASE ODBC Driver.
Also check the Drivers tab in the ODBC Admin. See what the actual file is listed for the driver.
sysybnt.dll
syodase.dll are unsupported drivers.
It would be to your advantage to open an incident with SAP for more complete support
Thank you,
Kevin

How to Configure Remote Connections To SQL Server 2008 R2 Express

Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!

My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
            // netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
            // netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo

Opening Excel Workbook Fails when run from Scheduled Task on Windows Server 2008 Rw

Hi,
I have a little vbs script that instantiates the Excel.Application object and then opens a work book to perform some tasks on it. The script runs fine when run from the command line. When I attempt to run it as a scheduled task (it is supposed to update
data that is pulled from a SQL Server at regular intervals), it fails with the following error:
Microsoft Office Excel cannot access the file 'c:\test\SampleWorkbook.xlsm'. There are several possible reasons: .....
The file does exist. The path reported in the error is correct. The account under which the task is running is the same account I use to run it from the command line. User Account Control is not enabled, and the task is set up to run with highest privileges.
When I run the same script through the Task Scheduler from a Windows Server 2003 machine, it works without issue.
I was just wondering if somebody on this forum has run into a similar issue in connection with Windows Server 2008 R2 and figured out what the magic trick is to make it work. I'm sure it is rights related, but I haven't quite figured out what which rights
are missing.
Thanks in advance for any advice you may have.

This is truly killing me ... trying to get it working on Windows Server 2012 without success.
I desperately need to automate running Excel macros in a "headless" environment, that is non-interactive, non-GUI, etc.
I can get it to work using Excel.Application COM, either via VBScript or Powershell, successfully on many other Windows systems in our environment - Windows Server 2008 R2, Windows 7 (32-bit), etc., -BUT-
The two servers we built out for running our automation process are Windows Server 2012 (SE) - and it just refuses to run on the 2012 servers - it gives the messages below from VBScript and PowerShell, respectively-
I have tried uninstalling and re-installing several different versions of Microsoft Excel (2007 Standard, 2010 Standard, 2010 Professional Plus, 32-bit vs. 64-bit, etc.), but it makes no difference.
Would be extremely grateful if any one out there has had any success in running Excel automation on Server 2012 in a non-interactive environment that they could share.
( I have tried adding the "%windir%\syswow64\config\systemprofile\desktop"
folder, which did fix the issue for me when testing on Windows Server 2008 R2, but sadly did not resolve it on Windows Server 2012 )
[VBScript error msg]
Z:\TestExcelMacro.vbs(35, 1) Microsoft Office Excel: Microsoft Office Excel cannot
access the file 'Z:\TestExcelMacro.xlsm'. There are several possible reasons:
• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open work
[Powershell error msg]
Exception calling "Add" with "0" argument(s): "Microsoft Office Excel cannot open or save any more documents because th
ere is not enough available memory or disk space.
To make more memory available, close workbooks or programs you no longer need.
To free disk space, delete files you no longer need from the disk you are saving to."
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation
You cannot call a method on a null-valued expression.
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Using drag and drop in remote desktop on windows server 2008

we running an application on windows server 2008 terminal services .. this application was support drag and drop functionality .. i understand that terminal services on windows 2008 is supported to drag and drop but is not happening !! even when i run remote desktop connection on this server the drag and the drop is not working !
i need to enable the drag and drop for windows 2008 terminal services ..
Thanks in advance

Hello Ayman,
If your requirement is to drag and drop files between local and remote sessions, Danny is right. Drag-and-drop feature is not supported in Windows Server 2008-based Terminal Server, which is a by-design behavior hard-coded in the current version of the Remote Desktop Protocol.
As a workaround, I recommend you to use copy-and-paste function instead of drag-and-drop. To enable the copy-and-paste between local and remote session, please enable the clipboard redirection in Windows Server 2008-based RDC. (In Windows Server 2003 environment, local drive redirection is needed.)
Hope it helps. Thanks.
Best Regards,
Lionel Chen

RH Server 9 compatibility with Windows Server 2008 SP2/SQL Server

Our tech support people are preparing for a first install of RH Server 9. They have asked me to find out whether there is a recent patch that would enable it to work with Windows Server 2008 SP2 64 bit and MS SQL Server 2008.
If there is not yet a patch, will there be one for this OS/DB combination in the future, and when?
This is in reference to the knowledgebase article at http://kb2.adobe.com/cps/884/cpsid_88483.html which gives a "not recommended" status to this combination.
Our infrastructure team would prefer to use this combination if it is possible.
Second question from the tech team: Do we need to separate the RoboHelp application from the database or can they both reside on the same server?

To answer your first question, no there is no patch to allow SQL Server 2008 to run on a 64 bit server. To answer your second question, I don't know. This is a user to user forum and therefore we are not party to any discussions on when or if a patch will be released. You could sumbit a feature request which the Adobe RoboHelp Product Manager will get. This will help advance your case. You can submit it here:
http://www.Adobe.com/cfusion/mmform/index.cfm?name=wishform&product=38
The RoboColum(n)
@robocolumn
Colum McAndrew

JDK and JRE comptability for Windows server 2008

Hi,
Could someone please let me know what are the JDK and JRE versions that are comptabile with Windows server 2008 ?
Thanks.

Hi,
For security purposes, the IP address for the Windows Update web site constantly changes and it is not a fixed address. Also, there is no official publication of the
IP addresses. We normally advise against defining IP addresses on the firewall for this purpose. Instead, we suggest either allowing all outbound connections to http & https ports or defining the DNS addresses as permitted destinations for traffic via
the firewall.
For up-to-date information about the IP's being used by Windows Update, use the DNS system, as this is the only reliable up to date source of information. If you use
DNS, make sure the following destination hosts are specified:
http://windowsupdate.microsoft.com
http://*.windowsupdate.microsoft.com
https://*.windowsupdate.microsoft.com
http://*.update.microsoft.com
https://*.update.microsoft.com
http://*.windowsupdate.com
http://download.windowsupdate.com
http://download.microsoft.com
http://*.download.windowsupdate.com
http://wustat.windows.com
http://ntservicepack.microsoft.com
http://stats.microsoft.com
https://stats.microsoft.com
Thanks for your understanding.
Best Regards,
Nina
This posting is provided "AS IS" with no warranties, and confers no rights.

Windows Server 2008 R2: Using PowerShell to send a MSI file to all workstations

Hello!
We are currently using Windows Server 2008 R2. In the upcoming months, we are releasing new software. Instead of touching all the machines with gpupdate /force, we would like to know if we could somehow use Windows PowerShell and send that
command to all the computers in our organization? We are currently in the process of using Group Policy Management to set up the new GPO. After we create them, we would like to send the MSI file to all workstations. I know it is SUPER easy to do within Windows
Server 2012... as I have read articles and seen screenshots. I am just having a hard time figuring out how to make it work with Windows Server 2008 R2.
Thanks!
Megan

New-PSSession -computername Computer
where Computer is one of your remote computers. If that succeeds, great! But I'm guessing it won't and enabling that on all of your computers would require more effort than what you're trying to accomplish in the first place.
Psexec is free to download and you don't have to deploy it:
http://technet.microsoft.com/en-us/sysinternals/bb897553.aspx
As far as identifying your target computers, it really depends on your environment. Get-ADComputer is effective, but the example I provided above would get literally every computer in your active directory - is this something you want to deploy to
any and all servers, workstations, etc? How big and complex is your AD? Is this something you need to coordinate with all your systems around about the same time, or can it be staggered? Do you expect your target computers not to reboot between
now and then? I know that's a lot of questions, but your question is loaded and not easy to answer without knowing more about your environment.
What about this?
http://technet.microsoft.com/en-us/library/jj134201.aspx
There is a requirement to have certain firewall exceptions on your target systems, but hopefully they are because that is the best approach.
I hope this post has helped!

Enable Local Area Connection in windows server 2008 r2

Similar Messages

Maybe you are looking for