App-V General Sequencing announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Server and Management announcements

I am asking for some help here in filling our an anonumous survey about App-V usage.

Traditionally, Microsoft is the only one that has any information regarding App-V usage out there, and basically Microsoft doesn't share that info (unless someone is bragging). So I am trying to gather some information to share with the community using an un-scientific survey. The survey is very short (10 questions), and does not ask you to identify yourself or your company. You can see all of the questions before you even start. It is just some basic questions to "get a feel" for what people are doing.

Let me be clear that this is not a Microsoft santioned survery and they have nothing to do with it. My company is requesting this information and will only use it to provide information back to the technical community. Any information gathered will only be used in aggregate form.

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Clients announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Documentation announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Add-ons announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This forum provides you an avenue where you can share knowledge, get questions answered, and learn from others with IT environments similar to yours who use the Resource Kit tools and other Add-ons to get the most out of their AppV deployments.

If you have any suggestions or feedback to the AppV product Add-ons like the resource kit tools, ADM template and so on, please feel free to post in this forum.

App-V General Sequencing announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Server and Management announcements

I am asking for some help here in filling our an anonumous survey about App-V usage.

Traditionally, Microsoft is the only one that has any information regarding App-V usage out there, and basically Microsoft doesn't share that info (unless someone is bragging). So I am trying to gather some information to share with the community using an un-scientific survey. The survey is very short (10 questions), and does not ask you to identify yourself or your company. You can see all of the questions before you even start. It is just some basic questions to "get a feel" for what people are doing.

Let me be clear that this is not a Microsoft santioned survery and they have nothing to do with it. My company is requesting this information and will only use it to provide information back to the technical community. Any information gathered will only be used in aggregate form.

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Clients announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Documentation announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

App-V Add-ons announcements

Thank you for posting in TechNet forum. Online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that can help you get the best answer to your question as quickly as possible.

When You Ask

1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

2. Provide all the necessary information in your initial post. The following information would be very helpful:

- Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

- Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

- Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

4. Keep within the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and gives the people who donate their time, warm and fuzzies.)

When answered

Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

This forum provides you an avenue where you can share knowledge, get questions answered, and learn from others with IT environments similar to yours who use the Resource Kit tools and other Add-ons to get the most out of their AppV deployments.

If you have any suggestions or feedback to the AppV product Add-ons like the resource kit tools, ADM template and so on, please feel free to post in this forum.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.