Can boot to VHD file be encrypted and still boot under Windows 7 or Windows Server 2008 R2?
Not according to requently Asked Questions: Virtual Hard Disks in Windows 7 and Windows Server 2008 R2
What is not supported for native boot when using VHDs?
Using compressed or encrypted VHDs for native boot. VHDs that have been compressed by NTFS or encrypted using Encrypting File System on the host volume are not supported for native boot.
Related
I am trying to figure out how to access an authenticated windows file share from .net core (supplying domain / username / password) from Linux.
I have a .NET framework based
sample project that does this in Windows operating system just fine. https://github.com/nddipiazza/SambaFetcher
(in particular
https://github.com/nddipiazza/SambaFetcher/blob/master/SmbFetcher/UNCAccess.cs )
But it relies on the NetApi32.dll directly so it will not work from Linux.
Is there some way from .NET core to do this authentication?
You can use this library: SMBLibrary which supports SMB2. I'll quote the description here:
SMBLibrary is an open-source C# SMB 1.0/CIFS, SMB 2.0 and SMB 2.1
server implementation.
SMBLibrary gives .NET developers an easy way to
share a directory / file system / virtual file system, with any
operating system that supports the SMB protocol.
SMBLibrary is
modular, you can take advantage of Integrated Windows Authentication
and the Windows storage subsystem on a Windows host or use independent
implementations that allow for cross-platform compatibility.
SMBLibrary shares can be accessed from any Windows version since
Windows NT 4.0.
It's mostly for coding a server, but it also has a client part here: https://github.com/TalAloni/SMBLibrary/tree/master/SMBLibrary/Client
I have an ASP-based application which provides real-time data from a local server to a small group of local users via mobile and desktop browsers (around 10 at any one time). Most of my installations use IIS running on Windows 7 Pro. Until now I have been using ajax short polling but am now prototyping changing the transport to SignalR.
Unfortunately it seems that using IIS on Windows 7 is not an option with since SignalR keeps a large number of connections open and in this configuration IIS has a concurrent connection limit of 10:
http://www.asp.net/signalr/overview/signalr-20/getting-started-with-signalr-20/supported-platforms
I am considering attempting to use IIS Express for my deployments. Is this a route worth pursuing? What are the pitfalls? Do I have any other options (other than to install Windows Server).
Thanks all
You can use self host signalR on a windows service see here for a sample
I use it on a Win7 machine
I have a analysis server database that runs Windows Server 2008 64 bits. And users reach cubes by msmdpump.dll. There is any problem before used FileMaker on same server. I could not analysis server database. I searched some documents that say I must change the application pool to 32 bit enabled. I changed OLAP web.config and added ISAPI filter. Also I read that I should use 32 bit msmdpump.dll but I run IIS 64 bit and how could you find 32 bit dll. Now I can not reached in any way. Could you help me what steps need to follow?
To install and configure OLAP Pump for IIS x64 connecting to an SSAS x64 instance, you use the msmdpump.dll of your x64 SSAS installation dir. To access an SSAS x86 instance, you use the msmdpump.dll of your x86 SSAS installation dir. The second variant requires you to enable 32 bit on your application pool.
A very nice guide of how to set up SSAS access via IIS can be found here:
Microsoft - Configure HTTP Access to SSAS via IIS
Many thanks and best regards
We have 64-bit Windows server and we need to explicitly enable the 32-bit mode in the Application Pool used by our web site, because the MS Jet Engine Data Provider used to import data from Excel does not run.
I am not sure, if we enable the 32-bit mode will we still get the advantage of 64-bit Server?
In IIS 7.x, there is a Advanced Settings property of the application pool called "Enable 32-bit Applications". If you run the application as a 32-bit applications it should be able to use 4 GB but obviously no more. So, in that respect, it can take advantage of running on a 64-bit server. On a 32-bit server (without special switches) it would only be able to use the 2GB of address space allocated to applications (the other 2 GB is presumed to be used by the OS).
ACE driver 64 bit is now available as a replacement of Jet driver. So you can use it instead,
http://blogs.msdn.com/b/psssql/archive/2010/01/21/how-to-get-a-x64-version-of-jet.aspx
(Read the last few paragraphs.)
In my ASP.NET application I have ftpdata folder, there is an MS Access 2010 file e.g. somename.accdb.
On my local computer (Win XP), there is no problem to connect with OleDb to this file and read write datas into and from tables.
But on server (Windows Server 2008), I cannot connect to the same file like on localhost.
Can you help me, please, where problem could be?
Finally, I found solution of problem.
There was not installed 2010 Data Connectivity Components on the server.
The windows user that your application pool is running in does probably not have read access to the directory/file
You need either direct access through the file system or SMB networking access (via a share defined on the server). If the FTP folder has an SMB share name, use that to get to it, but it's likely not shared (since it's purpose is for FTP access, not SMB access).
Installing the 2010 Data Connectivity Drivers does not seem to work, what worked for me was to set the corresponding website application pool in IIS to enable 32-Bit applications.
Official Microsoft Reference: