Windows 10: no event 9007, nhi on a Beckhoff IPC

We use joystick to control other devices.When plugged, it will generate a event ID: 9007, source: nhi; We use this event to call up a program. The logic tested perfect on windows 10 professional.But failed on windows 10 IoT Enterprise on a Beckhoff industrial PC. There's no event 9007.So how to turn on event 9007 on a windows 10 IoT Enterprise IPC?***moved from Windows / Windows 10 / ***

:)

 

Reimaging Widows 10 OEM from BECKHOFF

To whom it may concern

I read the "Reimaging licensed Microsoft software" document, however i am still not totally sure about it.

We are small startup company and buy for example 20 PC's from Beckhoff that have Windows 10 OEM installed on each one.

THe Windows 10 they supply have their logo and custom software preloaded.

I want to create a custom image that contains our logo, custom user accounts ect….

The process i follow is tas follow:

1. boot into one Windows 10 Beckhoff PC and customize Windows (create new user accounts, backgrounds ect…)

2. Boot from usb into Winpe and use dism to capture an image of the customised windows.

3. From winPE I use DISM to apply the image to the other 19 PC's.

Beckhoff has a volume license with Microsoft and according to me what I am doing is legal, because the OEM licence is the still the same for all PC's. It is the same as customising windows 10 on each PC individually,
or am i missing something here?

Sorry for grammar and English in advance.

Kind Regards

 

How to stop sharing folder for windows 10?

When I type "net share" under cmd, and find out a list of share name

C$ Default share

D$ Default share

IPC$ Remote IPC

ADMIN$ Remote Admin

I would like to know on how to stop the share status and disable Remote Admin & IPC

I would work with one PC not through network, how can I disable those remote setting?

Do you have any suggestions?

Thank you very much for any suggestions (^v^)

 

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.