Request a topic or
contact an Arke consultant
All posts tagged 'windows'

Arke Systems Blog

Useful technical and business information straight from Arke.

About the author

Author Name is someone.
E-mail me Send mail

Recent comments




The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2024

Windows 7 blocks files from external source

A while back I wrote to ArkeGlobal about windows 7 blocking my files.  It really should go here, so here it is with some updates.

 Original Sept 10, 2009

I downloaded an external dll source for a web application and adding the reference to my project yielded this error:

System.Security.SecurityException: Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.”

As it turns out Windows 7 security was blocking my downloaded dlls from running as a trusted source.  Going into the file system itself, I checked the permissions on the actually dll file and a message at the bottom says:

“This file came from another computer and might be blocked to help protect this computer.”

There is an ‘Unblock’ button right next to it and once I clicked it, it solved my issue.


Updated Oct 27, 2009

Since then, I ran into a similar issue but because of the way I had to build the project, every time it ran, it re-added that security back onto those dlls, so I found this:

Look at solution 3 and/or 4.

 Updated Mar 2011

This last encounter is for those of you that have large, and I do mean large files to copy down.  I had a particular instance where I had to download an upgrade zip file for DNN to lay over a pre-existing one.  When I downloaded and extracted all the contents of it to the client's machine, I had some blocked files.  I grumbled and unblocked it, tried again and got the same error.  Then I realized, Windows had blocked *every* file inside that zip.  I immediately started googling and every single article basically said, 'window's does not provide a way to unblock in bulk'.  So I stared at over 1700 files I had to right-click and unblock by hand with no one providing a solution.  I was about 1 hour in when I had an idea: 

"Right-click -> Properties" on the ZIP folder

It will have the same 'unblock' feature that all it's children are inheriting from.  Once I unblocked the zip, I extracted and all my files played nice again.


Posted by Nicole Rodriguez on Thursday, March 17, 2011 2:50 PM
Permalink | Comments (0) | Post RSSRSS comment feed

Hyper-V and Branching Virtual Machine Snapshots

So I have discovered what is potentially the coolest feature in Hyper-V.  So by now, you should be aware of the ability to make snapshots of your virtual environments.  This in and of itself is really nice.  However, there are some really awesome options with what you can do with these snapshots that make Hyper-V even more functional.

Imagine that you're doing a high-risk deployment to a production virtual machine. Things should go fine, but there's that chance that it doesn't.  How hard is it right now to clean up all those changes and revert?  Well, instead of doing that, take a snapshot of the VM right before you deploy.  If the deployment goes sideways, revert to the old snapshot and you're back in your old production environment in less than a minute. That's a lifesaver to someone like me. 

Let's take it a step further.  Let's do this in the development VM, but when things go sideways, let's also take a snapshot of the failed deployment before we revert.  Now make configuration changes and try to deploy again.  Let's say the deployment keeps failing, and you keep snapshotting.  You now have a branched set of snapshots that you can compare.  Maybe there's a common thread you overlooked before, but now you can track down. Better yet, you can almost instantly swap between all of your snapshots without having to take down the VM each time.

The fact that you can now branch snapshots of your VMs is a massive help to development environments, but also is great for IT.  Being able to set multiple configurations of a testing server allows infrastructure wonks really optimize new servers and services before they ever get into production.

So let me know, how do branching snapshots help you and your environment?

Posted by Wayne Walton on Wednesday, April 30, 2008 10:10 AM
Permalink | Comments (0) | Post RSSRSS comment feed

Moving Virtual Machines to Server 2008 and Hyper-V

Now that we've upgraded our VM infrastructure to Hyper-V, I thought I'd write up some of our experiences.  Trenton has already gone over some of the more technical details, like getting Debian configured, but I thought I'd start with the biggest potential hang-up I saw.  Simply put, if you're moving some old Virtual Server 2005 VMs to Hyper-V, there's to things you need to take into account:

  1. Uninstall the VS 2005 extensions from the client VM.
  2. Be prepared to reactivate Windows on the client VM.

Really, those are the only two things I found that are really important.  Everything else is really details.  Even though it's only in Release Candidate status right now, Hyper-V is already immensely better over Virtual Server 2005.  The VMs are faster, they're easier to manage, pretty much everything works better.

Posted by Wayne Walton on Tuesday, April 15, 2008 10:30 AM
Permalink | Comments (0) | Post RSSRSS comment feed

Installing Debian and Subversion on Hyper-V (DRAFT) - Updated

Part 1: Setting up the Hyper-V VM


The network adapter was the tricky part.  I mentioned the fix in this previous post:


Part 2: Installing Debian - Lenny

  1. Start the Debian install
  2. When it asks for you to create a user DO NOT use the same username as your AD account, this will just be confusing.  Use something else, or something like 'defaultdebianuser'.
  3. When it asks for software selection choose the following:
    • Standard System
  4. Now wait while it finishes the initial install.
  5. Reboot
  6. Login as root
  7. Install sudo  #>aptitude install sudo
  8. Setup your network settings:
    • #> sudo nano -w /etc/network/interfaces
    • Create a static entry such as:

      allow-hotplug eth0
      iface eth0 inet static

      auto eth0

    • Save and exit
    • #> sudo nano -w /etc/resolv.conf
    • Update the domain, search and nameserver fields
    • Save and exit
    • Restart the machine and re-login
  9. install the ssh server #> aptitude install ssh
  10. You can now ssh into the machine so you don't have to be on the actual box in order to finish setting subversion up.
Part 3: Connecting to the Active Domain

We have our base install of Debian now, and it's available via ssh.  We now need to install the necessary components for connecting to the Windows Domain.

  1. Modify the sources list accordingly
  2. #> sudo apt-get update
  3. #> sudo aptitude install libkrb53
  4. #> sudo aptitude install krb5-config
    • Asks for the AD server's hostname 
  5. #> sudo aptitude install samba
  6. #> sudo aptitude install winbind
  7. #> sudo aptitude install ntpdate
  8. #> sudo apt-get install ntp-server
  9. The previous items may ask for some configuration options, you can fill them in if you know them otherwise we'll be modifying the configuration files later...
  10. #> sudo /etc/init.d/samba stop
  11. #> sudo /etc/init.d/winbind stop
  12. #> sudo /etc/init.d/ntp stop
  13. #> sudo nano -w /etc/krb5.conf
    • Under the [realms] section add your AD controller's Hostname (if it's not already filled in from the configuration)

      kdc= ARKEDC


    • Look for the default_realm parameter and set it equal to your domain name.  The domain name MUST BE IN ALL CAPS.  For example, ARKESYSTEMS not arkesystems or
    • Save and Exit
  14. #> sudo ntpdate <ip of the time or AD server>
  15. #> sudo nano -w /etc/ntp.conf
    • Add a server like:
      • server <ip of the time or AD server>
    • Save and exit
  16. #> sudo /etc/init.d/ntp start
  17. check to see if this is working so far by:
    • #> ntpq -p
    • If it has your server in the list you good to keep going.
  18. #> sudo nano -w /etc/samba/smb.conf

      realm = ARKESYSTEMS.COM
      workgroup = ARKESYSTEMS
      security = ads
      idmap uid = 10000-20000
      idmap gid = 10000-20000
      template shell = /bin/bash
      template homedir = /home/%D/%U
      winbind use default domain = yes

    • Save and quit
  19. #> sudo nano -w /etc/nsswitch.conf
    • Add the winbind flag to the passwd and group field:

        passwd: files winbind
        group: files winbind

      1. In Lenny it will look like

      passwd: compat files winbind
      group: compat files winbind

  1. #> sudo ldconfig
  2. What we've done in the last few steps is synced the debian box with the time server.  They both need to be within a few seconds of each other in order to properly authenticate on the domain.  We then setup our user folders and samba authentication.  Finally we added the ability of Debian to validate against the AD for users.  We're now ready to attempt to join this machine to the domain. .
  3. ... But first add an entry for this machine in the Active Directory ...
  4. #> sudo net ads join -U "DOMAINADMIN"
  5. #> sudo /etc/init.d/samba start
  6. #> sudo /etc/init.d/winbind start
  7. use the getent passwd and getent group commands to check to see if they're listing the users and groups from your domain.  If they are not, double check your config files.
  8. Next we're going to configure PAM (Pluggable Authentication Module Subsystem)  This allows programs in the Linux environment to authenticate through the domain. We've got to update three configuration files to use the winbind extensions

      # sudo nano -w /etc/pam.d/common-account
      account sufficient
      account required

      # sudo nano -w /etc/pam.d/common-auth
      auth sufficient
      auth required use_first_pass

      # sudo /etc/pam.d/common-session

      session required skel=/etc/skel/ umask=0022
      session sufficient
      session required

  9. Now we need to edit our skeleton files for users who logon to debian for the first time.
    • #> cd /etc/skel
    • #> sudo mkdir .ssh
    • #> sudo nano -w .ssh/authorized_keys
    • Save and Exit
    • #> sudo chmod -R 744 .ssh
    • #> sudo nano -w .bashrc
    • add the line: umask 007 at the bottom, save and exit
    • #> sudo nano -w .bash_profile
    • change the umask to 007, save and exit
Part 4: Installing and Configuring Subversion
  1. #> sudo apt-get install subversion
  3. #> sudo apt-get install apache2
  4. #> sudo a2enmod dav_fs
  5. #> sudo /etc/init.d/apache2 force-reload

Categories: Server 2008
Posted by Trenton Adams on Tuesday, April 15, 2008 12:11 AM
Permalink | Comments (3) | Post RSSRSS comment feed

Hyper-V Miscellaneous

So I've been working on getting 2 VMs setup in Hyper-V today, a Windows 2003 server and a Debian Server.  Below are the issues I ran into and how to solve them.


Windows Server 2003 Standard

The main issue I ran into here was the inability to run the full Microsoft Update web site.  Basically when I clicked on Custom update, it would process for a while then end with an 0x80072ee2 error.

To fix this you have to disable TCPIP offloading.

  1. Run->regedit
  2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
  3. Add a REG_DWORD key/value pair:
    1. DisableTaskOffload = 1

Restart and you'll be able to access Microsoft's updates again.


Debian 4.0R3

The problem I ran into here, is that Debian does not detect the default Hyper-V virtual network adapter.  To fix this you'll need to go to you're VM's Settings page.

  1. Select the network adapter and delete it
  2. Select the Add Hardware option
  3. Add a new Legacy Network Adapter
  4. Modify settings on this as needed

You'll now be able to install Debian on the VM, and the installer will detect the network adapter


kick it on

Posted by Trenton Adams on Friday, April 11, 2008 3:58 PM
Permalink | Comments (0) | Post RSSRSS comment feed