how to ignore resolving $1 in awk as the positional parameter
 

i=$1
if [[ $# -eq 1 ]]
then
ssh -qt $i 'sudo dmidecode | grep -i Manufacturer | head -1 | awk -F"," '{print $1}'| awk -F":" '{print $2}' | tee -a test-raj'
else echo "Usage: Please give server name as 1st argument"
fi


Here is the result of execution:
dxxx-sa-unixmgmt@dxxxqxx01vsat01:~/raj # sh -x prepatch-script.sh CETQN1VTUTIxxx2
+ i=CETQN1VTUTIxxx2
+ [[ 1 -eq 1 ]]
+ ssh -qt CETQN1VTUTIxxx2 'sudo dmidecode | grep -i Manufacturer | head -1 | awk -F"," {print' 'CETQN1VTUTIxxx2}| awk -F":" {print' '} | tee -a test-raj'
awk: cmd. line:1: {print
awk: cmd. line:1: ^ unexpected newline or end of string
awk: cmd. line:1: {print
awk: cmd. line:1: ^ unexpected newline or end of string
dxxx-sa-unixmgmt@dexxqxx01vsat01:~/raj #

Wrong use of quotes. Try this:

Please use [code][/code] tags when displaying code/data.

I am not sure if veerain's suggestion will work? By using double quotes you open awk up to the shell parameters of $1 and $2, at least this is how it behaves inside a shell script.
In a shell script you could escape the dollar signs and still use single quotes, or perhaps see if switching the quotes around helps:
That being said, you could easily reduce the awk to a single call as well which eliminate some of then additional quotes.

You would also need to protect the $1 and $2 from being expanded by the outer shell.

You have better luck by putting the command in a variable. That way all the quotes get evaluated on the assignment:

And note that the embeded apostrophe quotes for the awk commands are escaped. This allows the leading quote (in front of the sudo) to continue to the end of the line and the trailing apostrophe quote.

This doesn't work, \ is not an escape character inside of single quotes.

ahh pud. messed up the quotes yet again. It's why I try to avoid nested quoting as much as possible.

So here is some simplification of the command:
This can now have a single set of quotes around the outside.