Remove all emojis from markdown documentation
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -102,7 +102,7 @@ $postData.dncConfig = {
|
||||
} | ConvertTo-Json -Compress
|
||||
```
|
||||
|
||||
#### GE Registry Architecture Data ⭐ **New in v3.0**
|
||||
#### GE Registry Architecture Data **New in v3.0**
|
||||
```powershell
|
||||
# DualPath Communication Settings
|
||||
$postData.dncDualPathEnabled = $true # Boolean: DualPath enabled
|
||||
@@ -204,7 +204,7 @@ UPDATE pc SET
|
||||
WHERE pcid = ?
|
||||
```
|
||||
|
||||
#### `pc_dnc_config` Table (Manufacturing Configuration) ⭐ **Enhanced in v3.0**
|
||||
#### `pc_dnc_config` Table (Manufacturing Configuration) **Enhanced in v3.0**
|
||||
```sql
|
||||
INSERT INTO pc_dnc_config (
|
||||
pcid, site, cnc, ncif, machinenumber, hosttype,
|
||||
@@ -217,7 +217,7 @@ INSERT INTO pc_dnc_config (
|
||||
ON DUPLICATE KEY UPDATE ...
|
||||
```
|
||||
|
||||
#### `machines` Table (Auto-Population) ⭐ **New in v3.2**
|
||||
#### `machines` Table (Auto-Population) **New in v3.2**
|
||||
```sql
|
||||
-- Machine records created from PC data
|
||||
INSERT INTO machines (
|
||||
|
||||
@@ -219,9 +219,9 @@ echo Creating configuration file...
|
||||
## Security Best Practices
|
||||
|
||||
### 1. Never Hardcode API Keys
|
||||
- ❌ Don't put API keys directly in scripts
|
||||
- ✅ Use environment variables or config files
|
||||
- ✅ Add `dashboard-config.json` to `.gitignore`
|
||||
- Don't put API keys directly in scripts
|
||||
- Use environment variables or config files
|
||||
- Add `dashboard-config.json` to `.gitignore`
|
||||
|
||||
### 2. Secure Storage on Client PCs
|
||||
```powershell
|
||||
|
||||
@@ -63,7 +63,7 @@ foreach ($interface in $networkInterfaces) {
|
||||
|
||||
---
|
||||
|
||||
## 🏭 Manufacturing/Shopfloor Configuration
|
||||
## Manufacturing/Shopfloor Configuration
|
||||
|
||||
### DNC (Direct Numerical Control) System Data
|
||||
| Field | Source | Type | Description |
|
||||
|
||||
@@ -107,7 +107,7 @@ Deploy-With-PsExec.bat
|
||||
#### Group Policy Deployment
|
||||
1. **Copy Scripts**: Place in network share accessible to all target computers
|
||||
2. **Create GPO**: New Group Policy Object for computer configuration
|
||||
3. **Add Startup Script**: Computer Configuration → Policies → Windows Settings → Scripts → Startup
|
||||
3. **Add Startup Script**: Computer Configuration Policies Windows Settings Scripts Startup
|
||||
4. **Configure Path**: Point to network share location of `Update-PC-CompleteAsset.bat`
|
||||
5. **Apply to OUs**: Link GPO to appropriate Organizational Units
|
||||
|
||||
@@ -221,7 +221,7 @@ Register-ScheduledTask -TaskName "GE Asset Collection" -Action $action -Trigger
|
||||
### Startup Script Integration
|
||||
```batch
|
||||
REM Add to computer startup scripts
|
||||
REM Computer Configuration → Policies → Windows Settings → Scripts → Startup
|
||||
REM Computer Configuration Policies Windows Settings Scripts Startup
|
||||
|
||||
@echo off
|
||||
timeout 60 >nul 2>&1
|
||||
@@ -307,7 +307,7 @@ Update-PC-CompleteAsset.ps1 -TestConnections
|
||||
whoami /priv
|
||||
|
||||
# Run as administrator
|
||||
Right-click → "Run as administrator"
|
||||
Right-click "Run as administrator"
|
||||
|
||||
# Service account configuration
|
||||
# Configure service account with:
|
||||
|
||||
@@ -80,8 +80,8 @@ function Get-PCType {
|
||||
- `$Hostname` (string) - Computer hostname
|
||||
|
||||
**Pattern Matching**:
|
||||
- `H###` patterns → `M###` (H123 → M123)
|
||||
- `G###` patterns → `M###` (G456 → M456)
|
||||
- `H###` patterns `M###` (H123 M123)
|
||||
- `G###` patterns `M###` (G456 M456)
|
||||
- Regex: `[HG](\d{3})`
|
||||
|
||||
**Returns**: `[string]` - Formatted machine number or `$null`
|
||||
@@ -162,7 +162,7 @@ $response = Invoke-RestMethod -Uri $uri -Method Get -TimeoutSec 30
|
||||
|
||||
**Payload Construction**: Creates comprehensive HTTP POST payload with structured data
|
||||
|
||||
**Manufacturing Data Handling** ⭐ **Enhanced in v3.0**:
|
||||
**Manufacturing Data Handling** **Enhanced in v3.0**:
|
||||
```powershell
|
||||
# DualPath and Registry Architecture Data
|
||||
$postData.dncDualPathEnabled = $geInfo.DualPathEnabled
|
||||
@@ -258,7 +258,7 @@ $dncConfig = @{
|
||||
|
||||
---
|
||||
|
||||
#### `Get-GERegistryInfo` ⭐ **New in v3.0**
|
||||
#### `Get-GERegistryInfo` **New in v3.0**
|
||||
**Purpose**: Comprehensive GE Aircraft Engines registry architecture analysis with DualPath detection
|
||||
**Returns**: `[hashtable]` - Complete registry architecture and DualPath configuration
|
||||
|
||||
|
||||
@@ -31,7 +31,7 @@ This directory contains comprehensive technical documentation for the GE Manufac
|
||||
- Error handling patterns and best practices
|
||||
- Code examples and usage patterns
|
||||
|
||||
### 🚀 [DEPLOYMENT_GUIDE.md](DEPLOYMENT_GUIDE.md)
|
||||
### [DEPLOYMENT_GUIDE.md](DEPLOYMENT_GUIDE.md)
|
||||
**Enterprise deployment strategies and procedures**
|
||||
- Single PC and multiple PC deployment methods
|
||||
- Enterprise integration (Group Policy, SCCM, Tanium)
|
||||
@@ -117,4 +117,4 @@ When updating scripts or functionality:
|
||||
|
||||
---
|
||||
|
||||
**📚 Comprehensive documentation for enterprise manufacturing asset management**
|
||||
** Comprehensive documentation for enterprise manufacturing asset management**
|
||||
@@ -443,7 +443,7 @@ Located in `winrm-https/` folder. These scripts configure secure WinRM over HTTP
|
||||
┌─────────────────────────────────────────────────────────────────┐
|
||||
│ ShopDB API Server │
|
||||
│ ┌──────────────────────────────────────────────────────────┐ │
|
||||
│ │ api.asp (IIS) → MySQL Database │ │
|
||||
│ │ api.asp (IIS) MySQL Database │ │
|
||||
│ └──────────────────────────────────────────────────────────┘ │
|
||||
└─────────────────────────────────────────────────────────────────┘
|
||||
```
|
||||
|
||||
@@ -86,7 +86,7 @@ The GE Manufacturing Asset Management System is a comprehensive PowerShell-based
|
||||
- Gateway and subnet mapping
|
||||
```
|
||||
|
||||
#### `Get-GERegistryInfo` ⭐ **New in v3.0**
|
||||
#### `Get-GERegistryInfo` **New in v3.0**
|
||||
```powershell
|
||||
# Dual registry architecture analysis
|
||||
- 32-bit registry path: HKLM:\SOFTWARE\GE Aircraft Engines
|
||||
@@ -109,7 +109,7 @@ The GE Manufacturing Asset Management System is a comprehensive PowerShell-based
|
||||
|
||||
### Phase 1: System Discovery
|
||||
```
|
||||
PC Environment → System Info Collection → Classification Engine
|
||||
PC Environment System Info Collection Classification Engine
|
||||
│
|
||||
├─ Hardware Identification (WMI/CIM)
|
||||
├─ Operating System Analysis
|
||||
@@ -119,7 +119,7 @@ PC Environment → System Info Collection → Classification Engine
|
||||
|
||||
### Phase 2: Manufacturing Intelligence
|
||||
```
|
||||
Registry Analysis → Manufacturing Config → Service Architecture
|
||||
Registry Analysis Manufacturing Config Service Architecture
|
||||
│
|
||||
├─ GE Aircraft Engines Detection (32-bit/64-bit)
|
||||
├─ DualPath Configuration Analysis
|
||||
@@ -129,7 +129,7 @@ Registry Analysis → Manufacturing Config → Service Architecture
|
||||
|
||||
### Phase 3: Network Topology
|
||||
```
|
||||
Network Interfaces → Machine Network Detection → Communication Analysis
|
||||
Network Interfaces Machine Network Detection Communication Analysis
|
||||
│
|
||||
├─ Active Interface Enumeration
|
||||
├─ Machine Network Identification (192.168.*.*)
|
||||
@@ -139,7 +139,7 @@ Network Interfaces → Machine Network Detection → Communication Analysis
|
||||
|
||||
### Phase 4: Data Consolidation
|
||||
```
|
||||
Collected Data → JSON Serialization → API Payload Construction
|
||||
Collected Data JSON Serialization API Payload Construction
|
||||
│
|
||||
├─ System Information Packaging
|
||||
├─ Manufacturing Configuration JSON
|
||||
@@ -149,7 +149,7 @@ Collected Data → JSON Serialization → API Payload Construction
|
||||
|
||||
### Phase 5: Centralized Storage
|
||||
```
|
||||
Dashboard API → Database Normalization → Relational Storage
|
||||
Dashboard API Database Normalization Relational Storage
|
||||
│
|
||||
├─ PC Table (Basic System Information)
|
||||
├─ PC_DNC_Config Table (Manufacturing Settings + Registry Architecture)
|
||||
@@ -158,9 +158,9 @@ Dashboard API → Database Normalization → Relational Storage
|
||||
└─ Machines Table (Auto-populated from PC machine numbers)
|
||||
```
|
||||
|
||||
### Phase 6: Machine Auto-Population ⭐ **New in v3.2**
|
||||
### Phase 6: Machine Auto-Population **New in v3.2**
|
||||
```
|
||||
PC Data Collection → Machine Number Extraction → Automated Machine Creation
|
||||
PC Data Collection Machine Number Extraction Automated Machine Creation
|
||||
│ │ │
|
||||
├─ Registry Scan ├─ Hostname Patterns ├─ Machine Records
|
||||
├─ DNC Detection ├─ GE Machine Numbers ├─ PC Relationships
|
||||
@@ -190,12 +190,12 @@ function Get-GEMachineNumber {
|
||||
# Pattern matching for GE hostname conventions
|
||||
if ($Hostname -match '[HG](\d{3})') {
|
||||
$machineNum = $Matches[1]
|
||||
return "M$machineNum" # Convert H123/G123 → M123
|
||||
return "M$machineNum" # Convert H123/G123 M123
|
||||
}
|
||||
}
|
||||
```
|
||||
|
||||
### Machine Auto-Population Architecture ⭐ **New in v3.2**
|
||||
### Machine Auto-Population Architecture **New in v3.2**
|
||||
|
||||
The system automatically creates machine records from shopfloor PC data using a multi-phase approach:
|
||||
|
||||
@@ -210,7 +210,7 @@ function Get-GEMachineNumber {
|
||||
|
||||
# Priority 2: Hostname pattern matching
|
||||
if ($Hostname -match '[HG](\d{3})') {
|
||||
return "M$($Matches[1])" # H3103 → M3103
|
||||
return "M$($Matches[1])" # H3103 M3103
|
||||
}
|
||||
}
|
||||
```
|
||||
@@ -260,7 +260,7 @@ END
|
||||
- **Multiple PC Handling**: Machine 0615 has 5 connected PCs
|
||||
- **Role Classification**: Control, HMI, Engineering, Backup PCs identified
|
||||
|
||||
### Dual Registry Architecture Handling ⭐ **New in v3.0**
|
||||
### Dual Registry Architecture Handling **New in v3.0**
|
||||
```powershell
|
||||
# Intelligent priority system prevents data overwrites
|
||||
if ($geInfo.DualPathEnabled -eq $null) {
|
||||
|
||||
Reference in New Issue
Block a user