search
Categories
Sponsors
VirtualMetric Hyper-V Monitoring, Hyper-V Reporting
Archive
Blogroll

Badges
MCSE
Community

Cozumpark Bilisim Portali
Fixing VirtualMetric Reports if VM has special characters
Posted in Windows Powershell | No Comment | 2,703 views | 21/02/2014 22:35

If you have special characters in your VM names, you may need to modify your XML files to fix reporting page.
Some characters (like &) may be special in XML, so you may need to change them to fix reporting page.

This is a simple script to search for “&” character in all XML files and replace them via “&”.

Thanks to Bill Stewart for Replace-FileString cmdlet. I made it a function to use in my case:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
function Replace-FileString
{
 
# Replace-FileString.ps1
# Written by Bill Stewart (bstewart@iname.com)
#
# Replaces strings in files using a regular expression. Supports
# multi-line searching and replacing.
 
#requires -version 2
 
<#
.SYNOPSIS
Replaces strings in files using a regular expression.
 
.DESCRIPTION
Replaces strings in files using a regular expression. Supports
multi-line searching and replacing.
 
.PARAMETER Pattern
Specifies the regular expression pattern.
 
.PARAMETER Replacement
Specifies the regular expression replacement pattern.
 
.PARAMETER Path
Specifies the path to one or more files. Wildcards are permitted. Each
file is read entirely into memory to support multi-line searching and
replacing, so performance may be slow for large files.
 
.PARAMETER LiteralPath
Specifies the path to one or more files. The value of the this
parameter is used exactly as it is typed. No characters are interpreted
as wildcards. Each file is read entirely into memory to support
multi-line searching and replacing, so performance may be slow for
large files.
 
.PARAMETER CaseSensitive
Specifies case-sensitive matching. The default is to ignore case.
 
.PARAMETER Multiline
Changes the meaning of ^ and $ so they match at the beginning and end,
respectively, of any line, and not just the beginning and end of the
entire file. The default is that ^ and $, respectively, match the
beginning and end of the entire file.
 
.PARAMETER UnixText
Causes $ to match only linefeed (\n) characters. By default, $ matches
carriage return+linefeed (\r\n). (Windows-based text files usually use
\r\n as line terminators, while Unix-based text files usually use only
\n.)
 
.PARAMETER Overwrite
Overwrites a file by creating a temporary file containing all
replacements and then replacing the original file with the temporary
file. The default is to output but not overwrite.
 
.PARAMETER Force
Allows overwriting of read-only files. Note that this parameter cannot
override security restrictions.
 
.PARAMETER Encoding
Specifies the encoding for the file when -Overwrite is used. Possible
values are: ASCII, BigEndianUnicode, Unicode, UTF32, UTF7, or UTF8. The
default value is ASCII.
 
.INPUTS
System.IO.FileInfo.
 
.OUTPUTS
System.String without the -Overwrite parameter, or nothing with the
-Overwrite parameter.
 
.LINK
about_Regular_Expressions
 
.EXAMPLE
C:\>Replace-FileString.ps1 '(Ferb) and (Phineas)' '$2 and $1' Story.txt
This command replaces the string 'Ferb and Phineas' with the string
'Phineas and Ferb' in the file Story.txt and outputs the file. Note
that the pattern and replacement strings are enclosed in single quotes
to prevent variable expansion.
 
.EXAMPLE
C:\>Replace-FileString.ps1 'Perry' 'Agent P' Ferb.txt -Overwrite
This command replaces the string 'Perry' with the string 'Agent P' in
the file Ferb.txt and overwrites the file.
#>
 
[CmdletBinding(DefaultParameterSetName="Path",
               SupportsShouldProcess=$TRUE)]
param(
  [parameter(Mandatory=$TRUE,Position=0)]
    [String] $Pattern,
  [parameter(Mandatory=$TRUE,Position=1)]
    [String] [AllowEmptyString()] $Replacement,
  [parameter(Mandatory=$TRUE,ParameterSetName="Path",
    Position=2,ValueFromPipeline=$TRUE)]
    [String[]] $Path,
  [parameter(Mandatory=$TRUE,ParameterSetName="LiteralPath",
    Position=2)]
    [String[]] $LiteralPath,
    [Switch] $CaseSensitive,
    [Switch] $Multiline,
    [Switch] $UnixText,
    [Switch] $Overwrite,
    [Switch] $Force,
    [String] $Encoding="ASCII"
)
 
begin {
  # Throw an error if $Encoding is not valid.
  $encodings = @("ASCII","BigEndianUnicode","Unicode","UTF32","UTF7",
                 "UTF8")
  if ($encodings -notcontains $Encoding) {
    throw "Encoding must be one of the following: $encodings"
  }
 
  # Extended test-path: Check the parameter set name to see if we
  # should use -literalpath or not.
  function test-pathEx($path) {
    switch ($PSCmdlet.ParameterSetName) {
      "Path" {
        test-path $path
      }
      "LiteralPath" {
        test-path -literalpath $path
      }
    }
  }
 
  # Extended get-childitem: Check the parameter set name to see if we
  # should use -literalpath or not.
  function get-childitemEx($path) {
    switch ($PSCmdlet.ParameterSetName) {
      "Path" {
        get-childitem $path -force
      }
      "LiteralPath" {
        get-childitem -literalpath $path -force
      }
    }
  }
 
  # Outputs the full name of a temporary file in the specified path.
  function get-tempname($path) {
    do {
      $tempname = join-path $path ([IO.Path]::GetRandomFilename())
    }
    while (test-path $tempname)
    $tempname
  }
 
  # Use '\r$' instead of '$' unless -UnixText specified because
  # '$' alone matches '\n', not '\r\n'. Ignore '\$' (literal '$').
  if (-not $UnixText) {
    $Pattern = $Pattern -replace '(?<!\\)\$', '\r$'
  }
 
  # Build an array of Regex options and create the Regex object.
  $opts = @()
  if (-not $CaseSensitive) { $opts += "IgnoreCase" }
  if ($MultiLine) { $opts += "Multiline" }
  if ($opts.Length -eq 0) { $opts += "None" }
  $regex = new-object Text.RegularExpressions.Regex $Pattern, $opts
}
 
process {
  # The list of items to iterate depends on the parameter set name.
  switch ($PSCmdlet.ParameterSetName) {
    "Path" { $list = $Path }
    "LiteralPath" { $list = $LiteralPath }
  }
 
  # Iterate the items in the list of paths. If an item does not exist,
  # continue to the next item in the list.
  foreach ($item in $list) {
    if (-not (test-pathEx $item)) {
      write-error "Unable to find '$item'."
      continue
    }
 
    # Iterate each item in the path. If an item is not a file,
    # skip all remaining items.
    foreach ($file in get-childitemEx $item) {
      if ($file -isnot [IO.FileInfo]) {
        write-error "'$file' is not in the file system."
        break
      }
 
      # Get a temporary file name in the file's directory and create
      # it as a empty file. If set-content fails, continue to the next
      # file. Better to fail before than after reading the file for
      # performance reasons.
      if ($Overwrite) {
        $tempname = get-tempname $file.DirectoryName
        set-content $tempname $NULL -confirm:$FALSE
        if (-not $?) { continue }
        write-verbose "Created file '$tempname'."
      }
 
      # Read all the text from the file into a single string. We have
      # to do it this way to be able to search across line breaks.
      try {
        write-verbose "Reading '$file'."
        $text = [IO.File]::ReadAllText($file.FullName)
        write-verbose "Finished reading '$file'."
      }
      catch [Management.Automation.MethodInvocationException] {
        write-error $ERROR[0]
        continue
      }
 
      # If -Overwrite not specified, output the result of the Replace
      # method and continue to the next file.
      if (-not $Overwrite) {
        $regex.Replace($text, $Replacement)
        continue
      }
 
      # Do nothing further if we're in 'what if' mode.
      if ($WHATIFPREFERENCE) { continue }
 
      try {
        write-verbose "Writing '$tempname'."
        [IO.File]::WriteAllText("$tempname", $regex.Replace($text,
          $Replacement), [Text.Encoding]::$Encoding)
        write-verbose "Finished writing '$tempname'."
        write-verbose "Copying '$tempname' to '$file'."
        copy-item $tempname $file -force:$Force -erroraction Continue
        if ($?) {
          write-verbose "Finished copying '$tempname' to '$file'."
        }
        remove-item $tempname
        if ($?) {
          write-verbose "Removed file '$tempname'."
        }
      }
      catch [Management.Automation.MethodInvocationException] {
        write-error $ERROR[0]
      }
    } # foreach $file
  } # foreach $item
} # process
 
end { }
}
 
$Files = Get-ChildItem -Path "C:\Program Files\VirtualMetric\webserver\http\xml\01" -Filter *.xml -Recurse
 
foreach ($File in $Files)
{
	$Path = $File.FullName
	$FileContent = Replace-FileString -Pattern "&" -Replacement "&#38;" -Path $Path
	$FileContent | Set-Content $Path
	Write-Host $Path is OK!
}

Please backup your XML directory first to avoid data corruption.



Leave a Reply