We have had the ability to publish an Excel Workbook to the web before but we needed to have either SharePoint or save the file as an HTML page and then post. Now with the Office Web Apps you can publish your Workbook to the web in either your website or a blog entry like this one. The advantage of this method is that when you update the data in the workbook it automatically updates the webpage that is displaying the workbook.

It might not be needed for everything but I think it is kind of cool.

Follow this link to get the directions on how to do this. You can also do this with PowerPoint.

http://office.microsoft.com/en-us/web-apps-help/embed-an-excel-workbook-on-a-web-page-HA102029502.aspx

Share

I had a student a number of years ago who was in a bunch of hot water with her manager. She had updated a critical spreadsheet for a co-worker who was on vacation, and in doing so, entered data right over the complex, nested, multi-dimensional formulas that took eons to create and perfect. Because the calculations were integral to day-to-day operations and were referenced by multiple workbooks, she instantly became persona non grata in her small office. She never saw it coming. She never saw that formulas were camouflaged by the values the cells. Because she trusted Excel, she believed what it displayed when she opened the workbook. She felt betrayed, because – as she saw it – Excel lied to her.

Those of us who are “in the know” understand that there were many red flags and visual cues along the way that went unheeded. Moreover if protection was properly applied by the author, she wouldn’t be in this mess in the first place. But, I understand her frustration.

In case you aren’t familiar with Excel’s reputation for not always showing the whole truth, here’s a scaled-down example of what my student experienced:

What is in cell A3?


“The number 3″, you say? “Duh”, you say? Not so fast!

Watch what happens when I click on that cell:


The Formula Bar tells the truth. The value 3 isn’t really what’s in that cell; a formula that adds whatever is in cell A1 with whatever is in cell A2 is. Obviously, not knowing this nuance can lead to a pretty big oops; hence, the situation that my student found herself in. That tidbit might be elementary to you. But does that knowledge alone solve the issue? Not unless you want to click on every cell in your worksheets just to ensure that everything is as it appears.

Here’s what you may not know: To identify all of the cells that contain formulas and functions in a worksheet, hold down the CTRL key while pressing the tilde ~ key (usually located above TAB).

Before CTRL + ~

After CTRL + ~

 

To return to normal display, use that key combination again.

Yup, it’s that simple, and it doesn’t matter which version you use. This ability has been available since the early days of Excel. If you’ve been using Excel forever and had no idea this was available, don’t beat yourself up about it. Hey, you don’t know what you don’t know, right?

If you have questions about this topic, please never hesitate to communicate. I can be reached via hferrise@t3training.com

Share

You don’t know what you don’t know, right? Here’s the kickoff for our YDKWYDK series of postings that highlight “hidden” tips/tricks/shortcuts/efficiency boosters/sanity savers from the Office suite of applications. In my many years of delivering training, I have discovered that even the most experienced, power-user types exhibit gaps in knowledge. Usually, it’s not because of lack of technical prowess or any deficiencies in skill set. It’s because they have never thought to ask the question. It’s because they have not run across the context needed to employ a particular tactic. It’s because the way they were able to “get something to work” actually does work most of the time. It’s because they don’t know what they don’t know.

I’ll let you in on a little secret – If you’ve ever thought “There’s gotta be a better way to do … “, you’re probably right. In most Microsoft applications, five to seven ways exist to accomplish any given task. Some strategies work more fluidly and intuitively than others, depending on mission. If your strategy works for you and provides you with the desired outcome, de facto, it works. Overall, there is no magic one-size-fits-all, “better” way of doing something, just ones that fit the objective more closely than others; but sometimes, the devil is in the details.

Not all of these postings will show strategies that are novel to you. But, if you keep checking back from time to time, you might find a few that are the forehead-smacking, why-didn’t-I-think-of-that, worth-the-price-of-admission types. We will update frequently, so if you think this info will help someone else, we’d love it if you spread the word.

Our objective is simple: to answer the questions that you never thought to ask. If we accomplish our objective and hit a nerve, please don’t beat yourself up about it. You don’t know what you don’t know, right?

Share

Ever wish there was a way to stop people from “Replying to All”  in Outlook? You know the scenario: someone from the company sends out an informational email and the next thing you know 25 people decide to Reply to All and the users of your company are flooded with emails that are just not relevant.

Well, Microsoft Research has the answer.

http://research.microsoft.com/en-us/projects/researchdesktop/noreplyall.aspx

This is a small add-on to Outlook 2007 or Outlook 2010, and it just might save you a headache from time to time.

Share

Service pack 1 for Exchange 2010 is finally here. There are many new features and a whole bunch of fixes.

The following documents are a good place to start:  What’s New in SP1, SP1 Release Notes, and Prerequisites

The Exchange team also has a decent article about the upgrade and some potential issues. Exchange 2010 SP1 FAQ and Known Issues

For the most part, it is a pretty simple upgrade to SP1. I do recommend that you take the time to verify any 3rd party applications that work with Exchange 2010 (Virus, Spam, or Archiving programs). Many of these applications take a little while to support the updated service pack. Since the update does modify the architecture of the core Exchange services, some of those 3rd party apps may have issues.

Here’s a matrix of the updates required, including download locations and file names:

Hotfix

Download

Windows Server 2008

Windows Server 2008 R2

Windows 7 & Windows Vista

979744
A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application
MSDN
or Microsoft Connect
Windows6.0-KB979744-x64.msu (CBS: Vista/Win2K8) Windows6.1-KB979744-x64.msu (CBS: Win7/Win2K8 R2)

N. A.

983440An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2

Request from CSS

Yes

Yes

N.A.

977624
AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista. Without this update, Active Directory Rights Management Services (AD RMS) features may stop working
Request from CSS using the “View and request hotfix downloads” link in the KBA | US-English Select the download for Windows Vista for the x64 platform.

N.A.

N.A.

979917Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode

Request from CSS using the Hotfix Request Web Submission Form or by phone (no charge)

Yes

N. A.

N. A.

973136,
FIX: ArgumentNullException exception error message when a .NET Framework 2.0 SP2-based application tries to process a response with zero-length content to an asynchronous ASP.NET Web service request: “Value cannot be null”.
Microsoft Connect Windows6.0-KB973136-x64.msu

N.A.

N. A.

977592
RPC over HTTP clients cannot connect to the Windows Server 2008 RPC over HTTP servers that have RPC load balancing enabled.
Request from CSS Select the download for Windows Vista (x64)

N.A.

N. A.

979099
An update is available to remove the application manifest expiry feature from AD RMS clients.
Download Center

N. A.

Windows6.1-KB979099-x64.msu

N. A.

982867
WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1
MSDN

N. A.

Windows6.1-KB982867-v2-x64.msu (Win7) X86: Windows6.1-KB982867-v2-x86.msu (Win7)
x64: Windows6.1-KB982867-v2-x64.msu (Win7)
977020FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.

Microsoft Connect

N. A.

N. A.

x64: Windows6.1-KB977020-v2-x64.msu
X86: Windows6.1-KB977020-v2-x86.msu
Share

The Remote Desktop Connection Manager (or RDCMan, for short) is a pretty cool, free tool from Microsoft to help manage all those remote desktop connections.

You can download the tool here

You can create multiple files with an .rdg extension.

Once you have created a file you can look at the settings.

The settings will allow you to manage logins, gateways, display settings, and other options for all of your connections.

Now just add your servers into the system. You can create groups for them and override the default settings with different connections options.

Once you have the servers added, you can see a preview of each one and just double click on one to connect to it. Switching to another server is as easy as clicking on that one.

Instead of having a bunch of windows open, you can manage all of the connections very easily with this free tool. Give it a try.

Share

PowerShell is this awesome tool that Microsoft is integrating to just about everything. Back to the command line we go. Scripting is really powerful and can really streamline a lot of processes.

One of most common questions I get is, “How do I run a script in PowerShell?”

This might seem really simple until you actually go a run a script.

In the following screen shot I am trying to run the script getver.ps1 which is in the directory ‘c:\temp\scripts’. Since PowerShell looks similar to the command shell you would think that you could just type the name of the script. When you do you get the first response. In PowerShell you have to type the whole path of the script, or if you are in the directory already you can use ‘.\scriptname to call the script. However, you will notice that that doesn’t work either.

Before you can run a script you have to set the execution policy. There are 4 levels.

  • Restricted – No scripts can be run. Windows PowerShell can be used only in interactive mode.
  • AllSigned – Only scripts signed by a trusted publisher can be run.
  • RemoteSigned – Downloaded scripts must be signed by a trusted publisher before they can be run.
  • Unrestricted – No restrictions; all Windows PowerShell scripts can be run

The default is Restricted. You can set your policy to AllSigned or RemoteSigned which works great in your environment to distribute scripts. If you are just testing and developing scripts you may want to use Unrestricted on that workstation. For a more information on script signing check out this article http://technet.microsoft.com/en-us/magazine/2008.04.powershell.aspx

As you can see I set the execution policy to Unrestricted and then ran the script. The script does run at this point at returns the version of the OS that is running.

Hopefully, this will help get those scripts running.

Share
© 2010 T3 Training Suffusion WordPress theme by Sayontan Sinha