How To Force Windows 7 To Open Excel Spreadsheets in Separate Windows…

2017-07-27T00:01:08+00:00 November 30th, 2011|Uncategorized|

As IT consultants, we occasionally find ourselves with large spreadsheets that need to be reviewed with human eyes (rather than by filters or scripts) for inspection or comparison, etc.

The other day I was quite frustrated while comparing a large amount of data between two Excel spreadsheets.  I had to constantly switch between each spreadsheet, or set them up side by side in the same window.  Since I have two monitors (of course), I wanted to be able to take advantage of ALL my screen real estate for my spreadsheet needs.  I searched a bit, and found a cool tip on the WhiteSites Blog from author Paul White (thanks Paul!) for my conundrum; and since Paul’s original post is mostly for Office 2003 (with updates for 2007/2010), I thought I should share a “readers digest” version of only the 2007/2010 version of it here.

Again, please note that these instructions are specifically for Excel 2007/2010. 

WARNING: Always backup your registry before making any changes. Do not attempt to perform these tasks if you are not comfortable with editing the registry.  Seriously.  Don’t.

  • Open Regedit
  • Navigate to the following registry key:
HKEY_CLASSES_ROOTExcel.Sheet.12shellOpencommand
  • The “(default)” value will be something like this:
"C:Program Files (x86)Microsoft OfficeOffice14EXCEL.EXE" /e
  • Append a “%1” to the end of the “(default)” value, making it:
"C:Program Files (x86)Microsoft OfficeOffice14EXCEL.EXE" /e "%1"
  • Rename the “command” value, which is right below the “(Default)” value, to “command2” or something else.
  • Rename the “ddeexec” key to “ddeexec2” or something else.

After you have done this, your Registry should like similar to this:

 

 …and with that, your Excel spreadsheets should now open in separate windows. 

Enjoy!

 

Happy Thanksgiving from the Coretek Family!

2011-11-23T00:19:43+00:00 November 23rd, 2011|Uncategorized|

From all of us in the Coretek family, we would like to take a moment to extend our deepest gratitude to each of our customers, partners, to each other, and to you; please know that we are deeply appreciative of every precious opportunity to which we are entrusted, and that we will do everything possible to continue to deserve your loyalty and trust.

Thank you.

We hope that you and your family have a wonderful Thanksgiving!

Easy Guest Access in Secure Wireless Networks

2017-07-27T00:01:08+00:00 November 17th, 2011|Uncategorized|

The Challenge

I’ve seen it happen; people sometimes hand out the corporation’s wireless security passphrases to allow visitors access to the internet.  Without the right equipment and design, this opens the internal network to the guest.  

Even though they’ve been warned that this behavior may put their infrastructure at risk, employees often want and need to give this access to their visitors.  It’s even more scary when policies are not in place to change pass phrases at regular intervals; possibly permitting the guest to retain the pass phrase for years without being noticed (obviously, I’m not talking about two factor authentication devices here).

One Solution

Several methods are available to allow guest access to the internet from your wireless network without sacrificing security.  Some require purchasing secondary wireless devices, and/or configuring VLANs throughout the network infrastructure.  Or if you’re lucky enough to have a Ruckus Wireless Controller, it’s built in.  Active Directory users can create their own guest passes on an easy-to-use webpage.

The Configuration

Within the Ruckus ZoneDirector, click the Configure tab.  Under the WLANs tab, create a new WLAN.  After the naming and description option, the Ruckus software allows three types of WLAN Usages (Standard, Guest Access, and Hotspot Service).  For Guest Access WLANs, the access is based on Guest Access Policies and access controls which are defined in Guest Access area of the Configuration tab.  Within here, you can define Authentication, compose your Terms of Use, and even Redirection of website requests.  Guest Pass Generation Authentication permissions can based either on a local database, or Microsoft’s Active Directory.  Most important within this section is Restricted Subnet Access.  The Ruckus setup acts as a proxy for guests thus easing the configuration by avoiding complex VLAN configurations throughout the networking infrastructure.

Problem solved!

 

Recognition From Symantec

2017-07-27T00:01:08+00:00 November 2nd, 2011|Uncategorized|

Symantec recently posted an item to their Endpoint Virtualization Community Blog, calling attention to a couple very nicely-done instructional videos done by fellow Coretek team member, Jeff Blakely (a.k.a. on YouTube).

Of course, we couldn’t be more proud of this recognition of Jeff’s talent by such a valued partner as Symantec; but we knew it all along.

😉

 Check out the Symantec blog item here:

http://www.symantec.com/connect/blogs/symantec-workspace-virtualization-youtube-videos?om_ext_cid=biz_con_email_2011_oct_26_news_youtube_videos

Thanks Symantec, and thanks Jeff!


Fatal error: Uncaught exception 'GuzzleHttp\Exception\ClientException' with message 'Client error: `POST https://dc.services.visualstudio.com/v2/track` resulted in a `400 Invalid instrumentation key` response: {"itemsReceived":1,"itemsAccepted":0,"errors":[{"index":0,"statusCode":400,"message":"Invalid instrumentation key"}]} ' in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113 Stack trace: #0 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Middleware.php(66): GuzzleHttp\Exception\RequestException::create(Object(GuzzleHttp\Psr7\Request), Object(GuzzleHttp\Psr7\Response)) #1 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(203): GuzzleHttp\Middleware::GuzzleHttp\{closure}(Object(GuzzleHttp\Psr7\Response)) #2 /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/promises/src/Promise.php(156): GuzzleHttp\Promi in /home/coretek/public_html/wp-content/plugins/application-insights/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php on line 113