Windows 10: excel reports

why when i open my excel reports it always ask me to sign into microsoft i cant copy the file into an another report

:)

 

Export All Administrative Events to Excel

To analyze events, from the Windows Event Viewer, there is a simple way to export all Administrative Events to Excel, with PowerShell.

Exporting all Administrative Events to Excel is a simple two Step process, as described here:

Step 1 - Create the Administrative Events View .xml file

1. Open Eventviewer (%windir%\system32\eventvwr.msc)
2. Navigate to: Event Viewer (Local) > Custom Views > Administrative Events
3. In the “Actions” pane select “Filter Current Custom View”.
4. Select the the XML tab.
5. Press Ctrl+A to select all the XML code of the Custom View.
6. Open a notepad, paste the selected code and save the file to your Desktop as AdmEvtView.xml

Step 2 - Create the csv file with the events

1. Download the ExportEvtCSV.zip file, which contains the script ExportEvtCSV.ps1 and unzip it, on your Desktop.
   It's not a fancy script, just basic PowerShell commands to create a csv file on the Desktop.
2. In Windows Search, type “ISE” (without the quotes) to open “Windows PowerShell ISE” and Run as administrator
   
3. To allow running the script, change the ExecutionPolicy, for this session. To do that, in the Console pane type:
   Code:
4. In the Windows PowerShell ISE, open and run the script: ExportEvtCSV.ps1
   The script will create a csv file with a name YYYYMMDD.HHMM.csv on the Desktop
5. When done, open the newly created .csv file, format the columns as needed and optionally save it as .xlsx, if you wish.

That’s it! You now have all the Administrative Events in Excel for filtering and further analysis.

Now to the more technical hard stuff... *Confused

There is a reason for running the script from within PowerShell ISE!

It would be great if everything was also working perfectly, when running the script from an elevated PowerShell too.

We can run it from an elevated PowerShell, which means that you just follow the Step 1, as above but for the Step 2 instead of the ISE you run the script from an elevated PowerShell.

The problem is that it will work only for anybody who has en-US format for the dates. Everyone else, who has another format (i.e. en-GB, fr-FR, el-GR etc.), the dates are not translated properly by Excel (although the script uses the –UseCulture switch) and remain as text in the en-US format.

I'm not sure if this a bug of the "export-csv" cmdlet, but although it runs the way it supposed to from within the ISE, from PowerShell there is a problem with the dates format.
As I haven’t found a way to overcome this obstacle, any suggestion from the PowerShell gurus of the forum (like my good friend Shawn @Brink, for instance), is welcome.

 

Guide: How to enable, use, and configure SLI on Linux.

I guess the next logical step would be to report on the performance you can get with SLI in Linux. That'd be my suggestion anyway.

 

Excel 2010 Document Inspector reports hidden sheets, not shown in VBA

Just a wild shot in the dark ...

Didn't macros get recorded in worksheets before Excel switched to VBA?
- I can't think how far back this was. Possibly Excel 4 in the early 1990s.
- Of course, this would make no sense at all if your workbook had been created since, say, Excel 2007.

If your workbook is older than that I'd suggest
1 Create a new blank one then, with both open at once, use the sheet tab Move or copy ... to copy each sheet to the new blank workbook.
2 In the VBEditor of the new workbook, create two new modules [Functions, Procedures] and then just copy the code text across from one to the other.
3 In the VBEditor window of the old one, in the Microsoft Excel objects list select each sheet in turn {including ThisWorkbook} then right-click and select View code. If there is anything in any of them, copy it to the same place in the new workbook.





Denis