Remove all emojis from markdown documentation

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

winrm-https/deployment-package/NETWORK_SHARE_DEPLOYMENT.md

@@ -32,7 +32,7 @@ New-SmbShare -Name "WinRM-HTTPS" -Path $deployPath -FullAccess "Everyone"
 **Or manually:**
 1. Create folder: `C:\Deployment\WinRM-HTTPS`
 2. Copy all files from `winrm-https` folder
-3. Right-click folder → Properties → Sharing → Advanced Sharing
+3. Right-click folder  Properties  Sharing  Advanced Sharing
 4. Check "Share this folder"
 5. Share name: `WinRM-HTTPS`
 6. Permissions: Give "Everyone" Read access (or specific security group)
@@ -49,10 +49,10 @@ Get-ChildItem "\\SERVER\WinRM-HTTPS"
 ```
 
 Expected files:
-- ✅ `Deploy-WinRM-HTTPS.bat`
-- ✅ `Setup-WinRM-HTTPS.ps1`
-- ✅ `wildcard-logon-ds-ge-com-20251017.pfx`
-- ✅ Other PS1 scripts
+-  `Deploy-WinRM-HTTPS.bat`
+-  `Setup-WinRM-HTTPS.ps1`
+-  `wildcard-logon-ds-ge-com-20251017.pfx`
+-  Other PS1 scripts
 
 ---
 
@@ -105,13 +105,13 @@ Include everything for troubleshooting:
 6. Wait for completion
 
 **Advantages:**
-- ✅ Simple - no copying needed
-- ✅ Always uses latest files
-- ✅ No local disk space used
+-  Simple - no copying needed
+-  Always uses latest files
+-  No local disk space used
 
 **Disadvantages:**
-- ⚠️ Requires network connectivity during install
-- ⚠️ Slower if network is congested
+-  Requires network connectivity during install
+-  Slower if network is congested
 
 ---
 
@@ -139,13 +139,13 @@ Deploy-WinRM-HTTPS.bat
 ```
 
 **Advantages:**
-- ✅ Faster execution
-- ✅ Works if network connection lost
-- ✅ Can verify files before running
+-  Faster execution
+-  Works if network connection lost
+-  Can verify files before running
 
 **Disadvantages:**
-- ⚠️ Uses local disk space
-- ⚠️ Extra copy step
+-  Uses local disk space
+-  Extra copy step
 
 ---
 
@@ -193,14 +193,14 @@ foreach ($hostname in $targetPCs) {
 ```
 
 **Advantages:**
-- ✅ Deploy to many PCs from one location
-- ✅ No physical access needed
-- ✅ Can run overnight/batch
+-  Deploy to many PCs from one location
+-  No physical access needed
+-  Can run overnight/batch
 
 **Disadvantages:**
-- ⚠️ Requires existing remote access (WinRM or admin shares)
-- ⚠️ More complex
-- ⚠️ Password visible in script (use secure credential management)
+-  Requires existing remote access (WinRM or admin shares)
+-  More complex
+-  Password visible in script (use secure credential management)
 
 ---
 
@@ -219,8 +219,8 @@ foreach ($hostname in $targetPCs) {
    - Edit GPO
 
 3. **Add Startup Script:**
-   - Computer Configuration → Policies → Windows Settings → Scripts
-   - Startup → Add
+   - Computer Configuration  Policies  Windows Settings  Scripts
+   - Startup  Add
    - Script: `\\DOMAIN\NETLOGON\Scripts\WinRM-HTTPS\Deploy-WinRM-HTTPS.bat`
 
 4. **Link GPO to OU:**
@@ -228,14 +228,14 @@ foreach ($hostname in $targetPCs) {
    - PCs will run script on next reboot
 
 **Advantages:**
-- ✅ Automated deployment
-- ✅ Centrally managed
-- ✅ Runs with SYSTEM privileges
+-  Automated deployment
+-  Centrally managed
+-  Runs with SYSTEM privileges
 
 **Disadvantages:**
-- ⚠️ Requires domain environment
-- ⚠️ Requires restart
-- ⚠️ Password handling more complex
+-  Requires domain environment
+-  Requires restart
+-  Password handling more complex
 
 ---
 
@@ -270,7 +270,7 @@ REM Set on each PC or via GPO
 setx WINRM_CERT_PASS "XqHuyaLZSyCYEcpsMz6h5" /M
 ```
 
-**⚠️ Never:**
+** Never:**
 - Hardcode password in batch file on network share (readable by everyone)
 - Email password in plaintext
 - Store password in unencrypted text file
@@ -293,7 +293,7 @@ Grant-SmbShareAccess -Name "WinRM-HTTPS" -AccountName "DOMAIN\IT Admins" -Access
 The certificate PFX file contains the private key. Protect it:
 
 1. **Use share permissions** to restrict access
-2. **Use certificate password** (you did ✅)
+2. **Use certificate password** (you did )
 3. **Monitor access** to the share
 4. **Delete from share** after deployment complete
 
@@ -315,7 +315,7 @@ The certificate PFX file contains the private key. Protect it:
 ```
 For each test PC:
 1. Navigate to \\SERVER\WinRM-HTTPS
-2. Right-click Deploy-WinRM-HTTPS.bat → Run as Administrator
+2. Right-click Deploy-WinRM-HTTPS.bat  Run as Administrator
 3. Enter password when prompted
 4. Verify success
 5. Test connection from management server
@@ -378,7 +378,7 @@ Write-Host "Share created: \\$env:COMPUTERNAME\WinRM-HTTPS"
 
 **On test PC (G1JJVH63ESF):**
 1. Open Explorer: `\\MANAGEMENT-SERVER\WinRM-HTTPS`
-2. Right-click `Deploy-WinRM-HTTPS.bat` → Run as Administrator
+2. Right-click `Deploy-WinRM-HTTPS.bat`  Run as Administrator
 3. Enter password: `XqHuyaLZSyCYEcpsMz6h5`
 4. Wait for completion
 
@@ -462,7 +462,7 @@ Get-SmbShareAccess -Name "WinRM-HTTPS"
 ### Problem: "Access Denied" running batch file
 
 **Solution:**
-- Right-click → Run as Administrator
+- Right-click  Run as Administrator
 - User must be local admin on PC
 - Check UAC settings
 
@@ -514,15 +514,15 @@ Save as `README.txt` in the share.
 
 **Best Practice for Your Scenario:**
 
-1. ✅ Create network share: `\\SERVER\WinRM-HTTPS`
-2. ✅ Include:
+1.  Create network share: `\\SERVER\WinRM-HTTPS`
+2.  Include:
    - `Deploy-WinRM-HTTPS.bat`
    - `Setup-WinRM-HTTPS.ps1`
    - `wildcard-logon-ds-ge-com-20251017.pfx`
-3. ✅ Deploy to 3-5 test PCs manually
-4. ✅ Verify each deployment
-5. ✅ Deploy to remaining PCs in batches
-6. ✅ Remove certificate from share when done
+3.  Deploy to 3-5 test PCs manually
+4.  Verify each deployment
+5.  Deploy to remaining PCs in batches
+6.  Remove certificate from share when done
 
 **Certificate Password Storage:**
 - Store in password manager
@@ -530,7 +530,7 @@ Save as `README.txt` in the share.
 - Use encrypted files for automation
 
 **The batch files handle:**
-- ✅ Administrator check
-- ✅ File verification
-- ✅ Error handling
-- ✅ User feedback
+-  Administrator check
+-  File verification
+-  Error handling
+-  User feedback

winrm-https/deployment-package/TEST-REMOTE-CONNECTION-GUIDE.md

@@ -503,13 +503,13 @@ Remove-PSSession $session
 
 ## Next Steps
 
-1. ✅ Run the updated deployment on test PC (with wildcard CN fix)
-2. ✅ Use these commands to test connectivity
-3. ✅ Verify remote commands work correctly
-4. ✅ If successful, deploy to 3-5 more PCs
-5. ✅ Test connectivity to all deployed PCs
-6. ✅ Document any issues in deployment logs
-7. ✅ Proceed with production rollout
+1.  Run the updated deployment on test PC (with wildcard CN fix)
+2.  Use these commands to test connectivity
+3.  Verify remote commands work correctly
+4.  If successful, deploy to 3-5 more PCs
+5.  Test connectivity to all deployed PCs
+6.  Document any issues in deployment logs
+7.  Proceed with production rollout
 
 ---